Automated occupant tracking systems and methods

ABSTRACT

An occupancy database is in electronic communication with a plurality of location-specific distributed computing entities to maintain real-time update occupancy data for various entities. As those entities relocate from one location to another (e.g., moving from one apartment to another), distributed computing entities associated with both the prior and new location of the entity transmit information to the occupancy database to reflect the changed location for the entity. The occupancy database also maintains communication data for the entities and/or locations associated with the entities, and the occupancy database may share that communication data with authorized mobile/user computing entities to enable communication between those authorized mobile/user computing entities and the particular entity or devices located at the entity&#39;s location.

BACKGROUND

Couriers, service providers, and other entities often encounter issuesin locating item/shipment or service recipients at multi-unit buildings(e.g., apartment buildings, condominium buildings, office buildings,and/or the like). One of the common causes of these delivery problemsstems from incomplete destination address information/data beingprovided to the service provider, either in the form of an item/shipmentdelivery address or a service request. For example, an item/shipmentdelivery address may include a street address, but may omit a relevantunit number for the item/shipment.

Even when the service provider knows the location within the multi-unitbuilding (based on memory alone, for example) for providing therequested services, missing a unit number may cause additionaldifficulties for the service provider. For example, the multi-unitbuilding may require a service provider to call a particular unit togain access to the building, and the building may require that theservice provider know the relevant unit number when requesting entry.

These and other service issues are particularly prevalent in the contextof delivering items/shipments to apartments, because apartment residentsoften move between units and/or buildings. The constant movement ofapartment residents may cause difficulties for delivery drivers toremember where particular residents live, and so those deliverypersonnel must rely more heavily on complete delivery addressinformation/data provided for items/shipments. Moreover, automateddelivery systems (e.g., drone-based delivery) require complete deliveryinformation/data be provided for all deliveries because the deliverymechanisms do not have the capability of simply remembering appropriatedelivery locations for various individuals.

Accordingly, a need exists for systems and methods for providingcomplete address information/data for various locations to ease accessfor providing services at those locations.

BRIEF SUMMARY

Various embodiments are directed to systems and methods for maintaininga real-time updated occupancy database of occupancy information/data forvarious locations and/or entities through real-time interactions among aplurality of distributed computing entities. The collection ofdistributed computing entities is configured to automatically provideand verify occupancy information/data for various entities upondetermination that the entity has moved to a new location. Thisoccupancy information/data may be provided to service providers en routeto provide services (e.g., delivery services) to those entities, therebyeasing contact with the entity and locating the entity to provide thedesired services.

Various embodiments are directed to an automated method for confirmingreal-time item recipient availability via a mobile computing entity incommunication with a central occupancy database. In certain embodiments,the method comprises: receiving, at the central database and from aplurality of service point devices located at respective service pointseach associated with a particular entity of a plurality of entities,real-time entity status data for each entity of the plurality ofentities; updating availability data stored in entity profilescorresponding to each entity of the plurality of entities to reflect thereal-time entity status for each entity; receiving, at the centraldatabase and from the mobile computing entity, a query for entity statusdata for a first entity; retrieving status data for the first entityfrom a first entity profile corresponding to the first entity; and upondetermining that the real-time status data for the first entityindicates that the first entity is available at a service pointassociated with the first entity, transmitting an indicator to themobile computing entity to complete delivery of an item at the servicepoint associated with the first entity.

In certain embodiments, the method further comprises, upon determiningthat the real-time status data for the first entity indicates that thefirst entity is unavailable, transmit an alternative indicator to themobile computing entity. The alternative indicator may identify analternative delivery location to complete delivery of the item.Moreover, the first entity profiles may comprise connectivity dataidentifying wireless communication types accepted by wireless electronicdevices associated with the first entity, and the method may furthercomprise: transmitting at least a portion of the connectivity data fromthe first entity profile to the mobile computing entity to enable themobile computing entity to wirelessly communicate with at least oneelectronic device associated with the first entity. The connectivitydata may identify wireless connectivity data for the service pointdevice associated with the first entity, and transmitting at least aportion of the connectivity data may comprise transmitting the wirelessconnectivity data to enable wireless communication between the mobilecomputing entity and the service point device. Moreover, in certainembodiments, the connectivity data identifies wireless connectivity datafor a mobile computing entity associated with the first entity, andwherein transmitting at least a portion of the connectivity datacomprises transmitting the wireless connectivity data to enable wirelesscommunication between the mobile computing entity associated with thedelivery personnel and the mobile computing entity associated with thefirst entity.

In certain embodiments, the query for first entity status data comprisesa first entity identifier and retrieving the status for the first entitycomprises: identifying an entity profile having the first entityidentifier; and retrieving the status data from the identified entityprofile.

Moreover, certain embodiments are directed to a computer system forconfirming real-time item recipient availability via a mobile computingentity in communication with a central occupancy database. The systemmay comprise: a mobile computing entity comprising at least onenon-transitory memory storage entity and at least one processor, whereinthe mobile computing entity is configured to generate an inquiry forentity status data for a first entity scheduled to receive an itemdelivery; and an occupancy database comprising at least onenon-transitory memory storage entity storing a plurality of entityprofiles corresponding to a plurality of entities, and wherein theoccupancy database is configured to: receive real-time status data froma plurality of service point devices each corresponding to a particularservice point and a particular entity; update entity profiles to reflectthe real-time status data for entities corresponding to each of theentity profiles; receive the inquiry for entity status data for thefirst entity; retrieve real-time status data for the first entity,wherein the real-time status data indicates whether the first entity islocated at a corresponding service point; and transmit the real-timestatus data to the mobile computing entity.

In certain embodiments the mobile computing entity is further configuredto: receive the real-time status data; and generate deliveryconfirmation data after receipt of the real-time status data. Moreover,each of the plurality of entity profiles may comprise connectivity datafor the corresponding entity, and wherein the occupancy database isconfigured to transmit connectivity data stored in the first entityprofile to the mobile computing entity; and the mobile computing entitymay be configured to, based at least in part on the connectivity data,establish a wireless communication connection between the mobilecomputing entity and the service point device associated with the firstentity.

In certain embodiments, the mobile computing entity is configured togenerate the delivery confirmation data upon establishing a wirelesscommunication connection with the service point device associated withthe first entity.

Certain embodiments are directed to a computer system for automaticallyconfirming real-time item recipient availability via a mobile computingentity in communication with a central occupancy database. In certainembodiments, the system comprises one or more non-transitory memorystorage areas and one or more processors, the one or more processorsbeing collectively configured to: receive, from a plurality of servicepoint devices located at respective service points each associated witha particular entity of a plurality of entities, real-time entity statusdata for each entity of the plurality of entities; update availabilitydata stored in entity profiles corresponding to each entity of theplurality of entities to reflect the real-time entity status for eachentity; receive, from the mobile computing entity, a query for entitystatus data for a first entity; retrieve, from the one or morenon-transitory memory storage areas, status data for the first entityfrom a first entity profile corresponding to the first entity; and upondetermining that the real-time status data for the first entityindicates that the first entity is available at a service pointassociated with the first entity, transmit an indicator to the mobilecomputing entity to complete delivery of an item at the service pointassociated with the first entity.

Various embodiments are directed to an automated method for coordinatingelectronic interactions among a plurality of distributed computingentities to maintain real-time occupancy data for a plurality ofentities. In certain embodiments, the method comprises: receiving, froma first distributed computing entity, occupancy update data for a firstentity, wherein the occupancy update data indicates that the firstentity moved to a first location; querying an occupancy database for afirst entity profile corresponding to the first entity, wherein theoccupancy database stores occupancy data for a plurality of entities incorresponding entity profiles; retrieving stored occupancy data from thefirst entity profile, wherein the stored occupancy data identifies asecond distributed computing entity associated with a second location;querying the second distributed computing entity associated with thesecond location for occupancy termination data corresponding to thefirst entity; and upon receipt of occupancy termination datacorresponding to the first entity, update the first occupancy profile toreflect the occupancy update data.

In various embodiments, the occupancy database is a blockchain database,and wherein retrieving stored occupancy data from the first entityprofile comprises retrieving data from a block of the blockchaingenerated prior in time and comprising occupancy data for the firstentity. Moreover, the first distributed computing entity may be a firstapartment management computing entity associated with a first apartmentcomplex and the second distributed computing entity may be a secondapartment management computing entity associated with a second apartmentcomplex. In certain embodiments, the method comprises steps forrequesting a manual override if occupancy termination data is notreceived, for example, within a defined period of time.

In certain embodiments, each of the plurality of entity profilesidentifies one or more prior locations occupied by the entity, andupdating the first occupancy profile may comprise: moving the storedoccupancy data to a prior occupancy portion of the first entity profile;and populating a current occupancy portion of the first entity profilewith the occupancy update data.

In certain embodiments, the entity profiles comprise contact data forcorresponding entities, and wherein updating the first occupancy profilecomprises updating the contact data stored in the first entity profile.Moreover, the occupancy update data may comprise identifier data for thefirst entity, and wherein querying the occupancy database for the firstentity profile corresponding to the first entity may comprise queryingthe occupancy database for an entity profile comprising the identifierdata.

Certain embodiments are directed to an automated system for coordinatingelectronic interactions among a plurality of distributed computingentities to maintain real-time occupancy data for a plurality ofentities. In certain embodiments, the system comprises: an occupancydatabase comprising a non-transitory memory, wherein the occupancydatabase stores a plurality of entity profiles each corresponding to aparticular entity and each comprising stored occupancy data forcorresponding entities; a first distributed computing entity configuredto: transmit occupancy update data to the occupancy database for a firstentity, wherein the occupancy update data indicates that the firstentity began an occupancy at a first occupancy location; and a seconddistributed computing entity associated with a second occupancy locationconfigured to: transmit occupancy termination data to the occupancydatabase for the first entity, wherein the occupancy termination dataindicates that the first entity terminated occupancy at the secondlocation; and wherein the occupancy database is configured to update afirst entity profile corresponding to the first entity to reflect theoccupancy update data upon receipt of the occupancy termination data forthe first entity.

In certain embodiments, the occupancy database is a distributed databasestored via a plurality of computing entities. Moreover, the occupancydatabase may be a blockchain database. The occupancy database may befurther configured to: in response to receipt of occupancy update datafor the first entity from the first distributed computing entity,retrieve a first entity profile corresponding to the first entity;identify the second distributed computing entity as a prior occupancylocation for the first entity; and transmit a query for occupancytermination data to the second distributed computing entity. Theoccupancy update data may comprise identifier data for the first entity,and wherein the occupancy database is configured to retrieve a firstentity profile based at least in part on the identifier data.

Various embodiments are directed to an automated computer system forcoordinating electronic interactions among a plurality of distributedcomputing entities to maintain real-time occupancy data for a pluralityof entities. In certain embodiments, the system comprises one or morenon-transitory memory storage areas and one or more processors, the oneor more processors may be collectively configured to: receive, from afirst distributed computing entity, occupancy update data for a firstentity, wherein the occupancy update data indicates that the firstentity moved to a first location; query an occupancy database for afirst entity profile corresponding to the first entity, wherein theoccupancy database stores occupancy data for a plurality of entities incorresponding entity profiles; retrieve stored occupancy data from thefirst entity profile, wherein the prior occupancy data identifies asecond distributed computing entity associated with a second location;query the second distributed computing entity associated with the secondlocation for occupancy termination data corresponding to the firstentity; and upon receipt of occupancy termination data corresponding tothe first entity, update the first occupancy profile to reflect theoccupancy update data.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 shows an example network of computing entities utilized inaccordance with various embodiments;

FIG. 2 shows a schematic diagram of an example occupancy computingentity according to various embodiments;

FIG. 3 shows a schematic diagram of an example distributed computingentity according to various embodiments;

FIG. 4 shows a schematic diagram of an example service point deviceaccording to various embodiments;

FIG. 5 shows an example entity profile according to various embodiments;

FIG. 6 is a flowchart showing an example process for updating an entityprofile according to various embodiments;

FIG. 7 is a flowchart showing an example process for delivering anitem/shipment according to a determined status of an item/shipmentrecipient according to various embodiments; and

FIG. 8 shows a schematic diagram of a user computing entity wirelesslycommunicating with one or more service point devices at a deliverylocation according to various embodiments.

DETAILED DESCRIPTION

The present disclosure more fully describes various embodiments withreference to the accompanying drawings. It should be understood thatsome, but not all embodiments are shown and described herein. Indeed,the embodiments may take many different forms, and accordingly thisdisclosure should not be construed as limited to the embodiments setforth herein. Rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Like numbersrefer to like elements throughout.

I. Overview

Occupancy information/data for various entities (e.g., residentialinformation/data for individuals, business locales for businessentities, and/or the like), is stored in an occupancy database embodiedas a database structure (e.g., a centrally stored relational database; adistributed relational database; a distributed blockchain database; acentralized blockchain database; and/or the like). The occupancyinformation/data is generated, maintained, and verified based oninformation/data received from a plurality of distributed data sources,such as electronic property records maintained by a municipality, leaseinformation/data maintained by a property manager, and/or the like. Theoccupancy information/data comprises a plurality of entity profiles,each entity profile corresponding to an entity (e.g., an individual, abusiness, and/or the like). Those entity profiles compriseinformation/data indicative of a current occupancy location for theentity, which may include street address, unit number, and/or the like.The entity profiles may additionally include contact information/datafor the entity (e.g., phone number, email address, social networkcontact information, and/or the like). The entity profiles mayadditionally comprise connection information/data for service pointdevices (e.g., Internet of Things (IOT) connected devices) within theunit/address/service point occupied by the particular entity. Theseservice point devices may provide additional information/data about theunit/address/service point for service providers, such as whether theentity is available at the unit/address/service point.

The occupancy information/data stored within the entity profile mayadditionally comprise information/data indicative of previousunits/addresses/service points occupied by the entity. Thisinformation/data may be stored in “blocks” of a blockchain, incolumns/rows of a relational database, and/or the like. Accordingly, theoccupancy information/data stored in the entity profile maintainsoccupancy information/data for entities over time.

At least portions of the information/data stored in the occupancydatabase may be accessible via network connected devices (e.g.,computing entities, mobile devices, and/or the like). As just oneexample, the information/data may be accessible via a speciallyconfigured computer program operating on a mobile device configured toquery and/or retrieve information/data from the occupancy database.Certain network connected devices may have read/write access to theinformation, and/or network connected devices may be limited to readaccess (e.g., read access for all information/data stored in theoccupancy database or read access for only a portion of information/datastored in the occupancy database). For example, the information/datastored in the occupancy database may be accessible to computing entities(e.g., mobile user computing entities) carried by delivery personnel,such that the occupancy database may be utilized to provide completedelivery information/data for items/shipments to be delivered to variousentities. The user computing entity carried by the delivery personnelmay be configured to automatically access the occupancy database toretrieve additional information/data regarding particular entities basedon information/data provided for upcoming/expected deliveries for thedelivery personnel.

Moreover, the occupancy database may be utilized to identify contactinformation/data for item/shipment recipients, such that the deliverypersonnel may contact item/shipment recipients before arriving at thedelivery destination. Furthermore, the occupancy database, throughconnections with service point devices (e.g., IOT devices) at variousunits/addresses/service points, may provide information/data to thedelivery personnel regarding whether an individual is available toaccept delivery at the unit/address/service point. Through these servicepoint devices, the occupancy information/data may enable the deliverypersonnel's computing entity to establish wireless connectivity withthese service point devices such that the delivery personnel's computingentity may directly retrieve information/data from these devices, mayprovide automatic, electronic delivery signatures evidencing a deliverypersonnel's visit to a particular location, and/or to operate variouselectronic devices (e.g., door locks, garage doors, and/or the like) atthe unit/address/service point to gain access to otherwise restrictedareas to complete a delivery.

In certain embodiments, the occupancy database may identify linksbetween various entity profiles to identify potential alternativedelivery locations if delivery to the entity is unsuccessful. Forexample, entity profiles for various entities may be linked withproperty management profiles, nearby delivery consolidation points,and/or the like. These linked profiles may identify potentialalternative delivery locations for items/shipments upon determining thatdelivery to the unit/address/service point corresponding to an entity isnot possible (e.g., no one available to accept delivery). Accordingly,the occupancy database may provide various information/data types toease delivery by delivery personnel.

II. Computer Program Products, Methods, and Computing Entities

Embodiments of the present invention may be implemented in various ways,including as computer program products that comprise articles ofmanufacture. A computer program product may include a non-transitorycomputer-readable storage medium storing applications, programs, programmodules, scripts, source code, program code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like (also referred to herein as executable instructions,instructions for execution, computer program products, program code,and/or similar terms used herein interchangeably). Such non-transitorycomputer-readable storage media include all computer-readable media(including volatile and non-volatile media).

In one embodiment, a non-volatile computer-readable storage medium mayinclude a floppy disk, flexible disk, hard disk, solid-state storage(SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solidstate module (SSM)), enterprise flash drive, magnetic tape, or any othernon-transitory magnetic medium, and/or the like. A non-volatilecomputer-readable storage medium may also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc(DVD), Blu-ray disc (BD), any other non-transitory optical medium,and/or the like. Such a non-volatile computer-readable storage mediummay also include read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory (e.g.,Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC),secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF)cards, Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium may also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), non-volatile random-accessmemory (NVRAM), magnetoresistive random-access memory (MRAM), resistiverandom-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory(SONOS), floating junction gate random access memory (FJG RAM),Millipede memory, racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium mayinclude random access memory (RAM), dynamic random access memory (DRAM),static random access memory (SRAM), fast page mode dynamic random accessmemory (FPM DRAM), extended data-out dynamic random access memory (EDODRAM), synchronous dynamic random access memory (SDRAM), double datarate synchronous dynamic random access memory (DDR SDRAM), double datarate type two synchronous dynamic random access memory (DDR2 SDRAM),double data rate type three synchronous dynamic random access memory(DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), TwinTransistor RAM (TTRAM), Thyristor RAM (T-RAM), Zero-capacitor (Z-RAM),Rambus in-line memory module (RIMM), dual in-line memory module (DIMM),single in-line memory module (SIMM), video random access memory (VRAM),cache memory (including various levels), flash memory, register memory,and/or the like. It will be appreciated that where embodiments aredescribed to use a computer-readable storage medium, other types ofcomputer-readable storage media may be substituted for or used inaddition to the computer-readable storage media described above.

As should be appreciated, various embodiments of the present inventionmay also be implemented as methods, apparatus, systems, computingdevices, computing entities, and/or the like. As such, embodiments ofthe present invention may take the form of an apparatus, system,computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. Thus, embodiments of the present inventionmay also take the form of an entirely hardware embodiment, an entirelycomputer program product embodiment, and/or an embodiment that comprisescombination of computer program products and hardware performing certainsteps or operations.

Moreover, certain embodiments may comprise and/or encompassblockchain-based database structures. These blockchain-based databasestructures may be embodied as distributed or centrally-managed ledgerdatabase structures. The distributed ledger database system may be apublic or private database, and may be stored on a plurality ofcomputing nodes to provide backup storage and/or to provide transactionverification mechanisms as discussed herein.

In certain embodiments, the distributed ledger system may comprise aplurality of blocks, wherein blocks generated later-in-time areelectronically linked to prior-generated blocks to provide a completelylinked block chain indicative of each transaction for whichinformation/data is stored in the distributed ledger. Each block maycomprise information/data identifying a particular parcel, a particularlocation, a particular entity, and/or the like, and information/datacorresponding to the parcel, location, or entity. Accordingly, byidentifying all blocks stored in the distributed ledger relating to aparticular parcel, location, and/or entity, a complete historical recordmay be established for the parcel, location, and/or entity.

In certain embodiments, each new block may be generated upon receipt ofinformation/data indicating a change in status of the parcel, location,and/or entity (e.g., received by a computer node). For example, eachtime a parcel moves from first carrier personnel to second carrierpersonnel or each time an entity moves from a first residential addressto a second residential address, a new block may be generated for thedistributed ledger. In certain embodiments, a plurality of computingentities may be configured to monitor, update, and/or verifyinformation/data for a plurality of parcels, entities, and/or locations.

Certain embodiments may comprise a plurality of linked distributedledgers each providing varying information/data regarding respectiveparcels, entities, and/or locations.

Embodiments of the present invention are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations may be implemented in the form of a computer programproduct, an entirely hardware embodiment, a combination of hardware andcomputer program products, and/or apparatus, systems, computing devices,computing entities, and/or the like carrying out instructions,operations, steps, and similar words used interchangeably (e.g., theexecutable instructions, instructions for execution, program code,and/or the like) on a computer-readable storage medium for execution.For example, retrieval, loading, and execution of code may be performedsequentially such that one instruction is retrieved, loaded, andexecuted at a time. In some exemplary embodiments, retrieval, loading,and/or execution may be performed in parallel such that multipleinstructions are retrieved, loaded, and/or executed together. Thus, suchembodiments can produce specifically-configured machines performing thesteps or operations specified in the block diagrams and flowchartillustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified instructions, operations, or steps.

III. Exemplary System Architecture

FIG. 1 provides an illustration of an exemplary embodiment of thepresent invention. As shown in FIG. 1, this particular embodiment mayinclude one or more occupancy computing entities 100, one or moreitems/shipments 102, one or more networks 105, one or more vehicles 107,one or more distributed computing entities 110, one or more servicepoint devices 117, one or more user computing entities 120, and/or thelike. Each of these components, entities, devices, systems, and similarwords used herein interchangeably may be in direct or indirectcommunication with, for example, one another over the same or differentwired or wireless networks. Additionally, while FIG. 1 illustrates thevarious system entities as separate, standalone entities, the variousembodiments are not limited to this particular architecture.

1. Exemplary Occupancy Computing Entity

FIG. 2 provides a schematic of an occupancy computing entity 100according to one embodiment of the present invention. In certainembodiments, the occupancy computing entity 100 may be maintained byand/or accessible by a carrier. A carrier may be a traditional carrier,such as United Parcel Service (UPS), FedEx, DHL, courier services, theUnited States Postal Service (USPS), Canadian Post, freight companies(e.g. truck-load, less-than-truckload, rail carriers, air carriers,ocean carriers, etc.), and/or the like. However, a carrier may also be anontraditional carrier, such as Amazon, Google, Uber, ride-sharingservices, crowd-sourcing services, retailers, and/or the like. Ingeneral, the terms computing entity, computer, entity, device, system,and/or similar words used herein interchangeably may refer to, forexample, one or more computers, computing entities, desktops, mobilephones, tablets, phablets, notebooks, laptops, distributed systems,gaming consoles (e.g., Xbox, Play Station, Wii), watches, glasses,iBeacons, proximity beacons, key fobs, radio frequency identification(RFID) tags, ear pieces, scanners, televisions, dongles, cameras,wristbands, kiosks, input terminals, servers or server networks, blades,gateways, switches, processing devices, processing entities, set-topboxes, relays, routers, network access points, base stations, the like,and/or any combination of devices or entities adapted to perform thefunctions, operations, and/or processes described herein. Suchfunctions, operations, and/or processes may include, for example,transmitting, receiving, operating on, processing, displaying, storing,determining, creating/generating, monitoring, evaluating, comparing,and/or similar terms used herein interchangeably. In one embodiment,these functions, operations, and/or processes can be performed on data,content, information, and/or similar terms used herein interchangeably.

As indicated, in one embodiment, the occupancy computing entity 100 mayalso include one or more communications interfaces 220 for communicatingwith various computing entities, such as by communicating data, content,information, and/or similar terms used herein interchangeably that canbe transmitted, received, operated on, processed, displayed, stored,and/or the like. For instance, the occupancy computing entity 100 maycommunicate with distributed computing entities 110, user computingentities 120, and/or the like.

As shown in FIG. 2, in one embodiment, the occupancy computing entity100 may include or be in communication with one or more processingelements 205 (also referred to as processors, processing circuitry,processing devices, and/or similar terms used herein interchangeably)that communicate with other elements within the occupancy computingentity 100 via a bus, for example. As will be understood, the processingelement 205 may be embodied in a number of different ways. For example,the processing element 205 may be embodied as one or more complexprogrammable logic devices (CPLDs), microprocessors, multi-coreprocessors, coprocessing entities, application-specific instruction-setprocessors (ASIPs), microcontrollers, and/or controllers. Further, theprocessing element 205 may be embodied as one or more other processingdevices or circuitry. The term circuitry may refer to an entirelyhardware embodiment or a combination of hardware and computer programproducts. Thus, the processing element 205 may be embodied as integratedcircuits, application specific integrated circuits (ASICs), fieldprogrammable gate arrays (FPGAs), programmable logic arrays (PLAs),hardware accelerators, other circuitry, and/or the like. As willtherefore be understood, the processing element 205 may be configuredfor a particular use or configured to execute instructions stored involatile or non-volatile media or otherwise accessible to the processingelement 205. As such, whether configured by hardware or computer programproducts, or by a combination thereof, the processing element 205 may becapable of performing steps or operations according to embodiments ofthe present invention when configured accordingly.

In one embodiment, the occupancy computing entity 100 may furtherinclude or be in communication with non-volatile media (also referred toas non-volatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In one embodiment, thenon-volatile storage or memory may include one or more non-volatilestorage or memory media 210, including but not limited to hard disks,ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, MemorySticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipedememory, racetrack memory, and/or the like. As will be recognized, thenon-volatile storage or memory media may store databases, databaseinstances, database management systems, data, applications, programs,program modules, scripts, source code, object code, byte code, compiledcode, interpreted code, machine code, executable instructions, and/orthe like. The terms database, database instance, database managementsystem, and/or similar terms used herein interchangeably may refer to astructured collection of records or data that is stored in acomputer-readable storage medium, such as via a relational database,hierarchical database, blockchain database, and/or network database.

In one embodiment, the occupancy computing entity 100 may furtherinclude or be in communication with volatile media (also referred to asvolatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In one embodiment, thevolatile storage or memory may also include one or more volatile storageor memory media 215, including but not limited to RAM, DRAM, SRAM, FPMDRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM,T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory,and/or the like. As will be recognized, the volatile storage or memorymedia may be used to store at least portions of the databases, databaseinstances, database management systems, data, applications, programs,program modules, scripts, source code, object code, byte code, compiledcode, interpreted code, machine code, executable instructions, and/orthe like being executed by, for example, the processing element 205.Thus, the databases, database instances, database management systems,data, applications, programs, program modules, scripts, source code,object code, byte code, compiled code, interpreted code, machine code,executable instructions, and/or the like may be used to control certainaspects of the operation of the occupancy computing entity 100 with theassistance of the processing element 205 and operating system.

As indicated, in one embodiment, the occupancy computing entity 100 mayalso include one or more communications interfaces 220 for communicatingwith various computing entities, such as by communicating data, content,information, and/or similar terms used herein interchangeably that canbe transmitted, received, operated on, processed, displayed, stored,and/or the like. Such communication may be executed using a wired datatransmission protocol, such as fiber distributed data interface (FDDI),digital subscriber line (DSL), Ethernet, asynchronous transfer mode(ATM), frame relay, data over cable service interface specification(DOCSIS), or any other wired transmission protocol. Similarly, theoccupancy computing entity 100 may be configured to communicate viawireless external communication networks using any of a variety ofprotocols, such as general packet radio service (GPRS), Universal MobileTelecommunications System (UMTS), Code Division Multiple Access 2000(CDMA2000), CDMA2000 1×(1×RTT), Wideband Code Division Multiple Access(WCDMA), Time Division-Synchronous Code Division Multiple Access(TD-SCDMA), Long Term Evolution (LTE), Evolved Universal TerrestrialRadio Access Network (E-UTRAN), Evolution-Data Optimized (EVDO), HighSpeed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA),IEEE 802.11 (Wi-Fi), Wi-Fi Direct, 802.16 (WiMAX), ultra wideband (UWB),infrared (IR) protocols, near field communication (NFC) protocols,Bluetooth protocols, Wibree, Home Radio Frequency (HomeRF), SimpleWireless Abstract Protocol (SWAP), wireless universal serial bus (USB)protocols, and/or any other wireless protocol.

Although not shown, the occupancy computing entity 100 may include or bein communication with one or more input elements, such as a keyboardinput, a mouse input, a touch screen/display input, motion input,movement input, audio input, pointing device input, joystick input,keypad input, and/or the like. The occupancy computing entity 100 mayalso include or be in communication with one or more output elements(not shown), such as audio output, video output, screen/display output,motion output, movement output, and/or the like.

As will be appreciated, one or more of the occupancy computing entity's100 components may be located remotely from other occupancy computingentity 100 components, such as in a distributed system. Furthermore, oneor more of the components may be combined and additional componentsperforming functions described herein may be included in the occupancycomputing entity 100. Thus, the occupancy computing entity 100 can beadapted to accommodate a variety of needs and circumstances. As will berecognized, these architectures and descriptions are provided forexemplary purposes only and are not limited to the various embodiments.

2. Exemplary Vehicle

In various embodiments, the term vehicle 107 is used generically. Forexample, a carrier/transporter vehicle 107 may be a manned or unmannedtractor, a truck, a car, a motorcycle, a moped, a Segway, a bicycle, agolf cart, a hand truck, a cart, a trailer, a tractor and trailercombination, a van, a flatbed truck, a vehicle, an unmanned aerialvehicle (UAV) (e.g., a drone), an airplane, a helicopter, a boat, abarge, and/or any other form of object for moving or transporting peopleand/or items/shipments (e.g., one or more packages, parcels, bags,containers, loads, crates, items banded together, vehicle parts,pallets, drums, the like, and/or similar words used hereininterchangeably). In one embodiment, each vehicle 107 may be associatedwith a unique vehicle identifier (such as a vehicle ID) that uniquelyidentifies the vehicle 107. The unique vehicle ID (e.g., trailer ID,tractor ID, vehicle ID, and/or the like) may include characters, such asnumbers, letters, symbols, and/or the like. For example, an alpha,numeric, or alphanumeric vehicle ID (e.g., “AS”) may be associated witheach vehicle 107. In another embodiment, the unique vehicle ID may bethe license plate, registration number, or other identifyinginformation/data assigned to the vehicle 107. As noted above, ininstances where the vehicle is a carrier vehicle, the vehicle may be aself-driving delivery vehicle or the like. Thus, for the purpose of thepresent disclosure, the term driver of a delivery vehicle may be used torefer to a carrier personnel who drives a delivery vehicle and/ordelivers items/shipments therefrom, an autonomous system configured todeliver items/shipments (e.g., a robot configured to transportitems/shipments from a vehicle to a service point such as a customer'sfront door or other service point), and/or the like.

Various computing entities, devices, and/or similar words used hereininterchangeably can be associated with the vehicle 107, such as a datacollection device or other computing entities. In general, the termscomputing entity, entity, device, system, and/or similar words usedherein interchangeably may refer to, for example, one or more computers,computing entities, desktops, mobile phones, tablets, phablets,notebooks, laptops, distributed systems, gaming consoles (e.g., Xbox,Play Station, Wii), watches, glasses, iBeacons, proximity beacons, keyfobs, RFID tags, ear pieces, scanners, televisions, dongles, cameras,wristbands, kiosks, input terminals, servers or server networks, blades,gateways, switches, processing devices, processing entities, set-topboxes, relays, routers, network access points, base stations, the like,and/or any combination of devices or entities adapted to perform thefunctions, operations, and/or processes described herein. The datacollection device may collect telematics information/data (includinglocation information/data) and transmit/send the information/data to anonboard computing entity, a distributed computing entity, and/or variousother computing entities via one of several communication methods.

In one embodiment, the data collection device may include, be associatedwith, or be in wired or wireless communication with one or moreprocessors (various exemplary processors are described in greater detailbelow), one or more location-determining devices or one or more locationsensors (e.g., Global Navigation Satellite System (GNSS) sensors), oneor more telematics sensors, one or more real-time clocks, a J-Busprotocol architecture, one or more electronic control modules (ECM), oneor more communication ports for receiving telematics information/datafrom various sensors (e.g., via a CAN-bus), one or more communicationports for transmitting/sending information/data, one or more RFIDtags/sensors, one or more power sources, one or more data radios forcommunication with a variety of communication networks, one or morememory modules 410, and one or more programmable logic controllers(PLC). It should be noted that many of these components may be locatedin the vehicle 107 but external to the data collection device.

In one embodiment, the one or more location sensors, modules, or similarwords used herein interchangeably may be one of several components inwired or wireless communication with or available to the data collectiondevice. Moreover, the one or more location sensors may be compatiblewith GPS satellites, such as Low Earth Orbit (LEO) satellite systems,Department of Defense (DOD) satellite systems, the European UnionGalileo positioning systems, Global Navigation Satellite systems(GLONASS), the Chinese Compass navigation systems, Indian RegionalNavigational satellite systems, and/or the like. Furthermore, the one ormore location sensors may be compatible with Assisted GPS (A-GPS) forquick time to first fix and jump start the ability of the locationsensors to acquire location almanac and ephemeris data, and/or becompatible with Satellite Based Augmentation System (SBAS) such as WideArea Augmentation System (WAAS), European Geostationary NavigationOverlay Service (EGNOS), and/or MTSAT Satellite Augmentation System(MSAS), GPS Aided GEO Augmented Navigation (GAGAN) to increase GPSaccuracy. This information/data can be collected using a variety ofcoordinate systems, such as the Decimal Degrees (DD); Degrees, Minutes,Seconds (DMS); Universal Transverse Mercator (UTM); Universal PolarStereographic (UPS) coordinate systems; and/or the like. Alternatively,triangulation may be used in connection with a device associated with aparticular vehicle 107 and/or the vehicle's operator and with variouscommunication points (e.g., cellular towers or Wi-Fi access points)positioned at various locations throughout a geographic area to monitorthe location of the vehicle 107 and/or its operator. The one or morelocation sensors may be used to receive latitude, longitude, altitude,heading or direction, geocode, course, position, time, and/or speed data(e.g., referred to herein as telematics information/data and furtherdescribed herein below). The one or more location sensors may alsocommunicate with the occupancy computing entity, the data collectiondevice, distributed computing entity, user computing entity, and/orsimilar computing entities.

As indicated, in addition to the one or more location sensors, the datacollection device may include and/or be associated with one or moretelematics sensors, modules, and/or similar words used hereininterchangeably. For example, the telematics sensors may include vehiclesensors, such as engine, fuel, odometer, hubometer, tire pressure,location, weight, emissions, door, and speed sensors. The telematicsinformation/data may include, but is not limited to, speed data,emissions data, RPM data, tire pressure data, oil pressure data, seatbelt usage data, distance data, fuel data, idle data, and/or the like(e.g., referred to herein as telematics information/data). Thetelematics sensors may include environmental sensors, such as airquality sensors, temperature sensors, and/or the like. Thus, thetelematics information/data may also include carbon monoxide (CO),nitrogen oxides (NOx), sulfur oxides (SOx), Ethylene Oxide (EtO), ozone(O₃), hydrogen sulfide (H₂S) and/or ammonium (NH₄) data, and/ormeteorological data (e.g., referred to herein as telematicsinformation/data).

In one embodiment, the ECM may be one of several components incommunication with and/or available to the data collection device. TheECM, which may be a scalable and subservient device to the datacollection device, may have data processing capability to decode andstore analog and digital inputs from vehicle systems and sensors. TheECM may further have data processing capability to collect and presenttelematics information/data to the J-Bus (which may allow transmissionto the data collection device), and output standard vehicle diagnosticcodes when received from a vehicle's J-Bus-compatible on-boardcontrollers 440 and/or sensors.

As indicated, a communication port may be one of several componentsavailable in the data collection device (or be in or as a separatecomputing entity). Embodiments of the communication port may include anInfrared Data Association (IrDA) communication port, a data radio,and/or a serial port. The communication port may receive instructionsfor the data collection device. These instructions may be specific tothe vehicle 107 in which the data collection device is installed,specific to the geographic area in which the vehicle 107 will betraveling, specific to the function the vehicle 107 serves within afleet, and/or the like. In one embodiment, the data radio may beconfigured to communicate in accordance with multiple wirelesscommunication standards and protocols, such as UMTS, CDMA2000, 1×RTT,WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IR,NFC, Bluetooth, USB, Wibree, HomeRF, SWAP, and/or the like. Similarly,the distributed computing entity 110 may operate in accordance withmultiple wired communication standards and protocols, such as thosedescribed above with regard to the occupancy computing entity 100 via anetwork interface 320.

3. Exemplary Item/Shipment

An item/shipment 102 may be any tangible and/or physical object. Suchitems/shipments 102 may be picked up and/or delivered by acarrier/transporter. In one embodiment, an item/shipment 102 may be orbe enclosed in one or more packages, parcels, bags, containers, loads,crates, items banded together, vehicle parts, pallets, drums, the like,and/or similar words used herein interchangeably. Such items/shipments102 may include the ability to communicate (e.g., via a chip (e.g., anintegrated circuit chip), RFID, NFC, Bluetooth, Wi-Fi, and any othersuitable communication techniques, standards, or protocols) with oneanother and/or communicate with various computing entities for a varietyof purposes. For example, the item/shipment 102 may be configured tocommunicate with a service point device 117 using a short/long rangecommunication technology, as described in more detail below. Further,such items/shipments 102 may have the capabilities and components of thedescribed with regard to the occupancy computing entities 100, networks105, vehicles 107, distributed computing entities 110, user computingentities 120, and/or the like. For example, the item/shipment 102 may beconfigured to store item/shipment information/data. In exampleembodiments, the item/shipment information/data may comprise one or moreof a consignee name/identifier, an item/shipment identifier, a servicepoint (e.g., delivery location/address, pick-up location/address),instructions for delivering the item/shipment, an item/shipment deliveryauthorization code, information/data regarding if a service point device117 is present at the service point, and/or the like. In this regard, insome example embodiments, an item/shipment may communicate send “to”address information/data, received “from” address information/data,unique identifier codes, and/or various other information/data. In oneembodiment, each item/shipment may include an item/shipment identifier,such as an alphanumeric identifier. Such item/shipment identifiers maybe represented as text, barcodes, tags, character strings, Aztec Codes,MaxiCodes, Data Matrices, Quick Response (QR) Codes, electronicrepresentations, and/or the like. A unique item/shipment identifier(e.g., 123456789) may be used by the carrier to identify and track theitem/shipment as it moves through the carrier's transportation network.Further, such item/shipment identifiers can be affixed toitems/shipments by, for example, using a sticker (e.g., label) with theunique item/shipment identifier printed thereon (in human and/or machinereadable form) or an RFID tag with the unique item/shipment identifierstored therein.

4. Exemplary Distributed Computing Entity

FIG. 3 provides an illustrative schematic representative of adistributed computing entity 110 that can be used in conjunction withembodiments of the present invention. In one embodiment, the distributedcomputing entities 110 may be operated by one or more carrier customers,one or more building managers, one or more municipality property recordsoffices, and/or the like. In certain embodiments, a carrier customer maybe a consignor (entity sending an item/shipment 102) or a consignee(intended recipient of an item/shipment 102). In example embodiments, adistributed computing entity 110 may be registered with one or moreservice point devices 117 (or a service point device 117 may beregistered with the distributed computing entity 110) such that theservice point device 117 may provide notifications (e.g., doorbellactivation notifications) to an individual operating the distributedcomputing entity 110. In example embodiments, a distributed computingentity 110 may be configured to monitor status information/datagenerated by the one or more service point devices 117, such as whethera service point device 117 detects the presence of aunit/address/service point occupant. In certain embodiments, thedistributed computing entity 110 may be in communication with aplurality of service point devices 117, such as service point devices117 associated with a plurality of building units (e.g., apartments,condominiums, offices, and/or the like).

In one embodiment, a distributed computing entity 110 may include one ormore components that are functionally similar to those of the occupancycomputing entity 100, item/shipment 102, vehicle 107, user computingentity 120, and/or the like. In general, the terms device, system,computing entity, entity, and/or similar words used hereininterchangeably may refer to, for example, one or more computers,computing entities, desktops, mobile phones, tablets, phablets,notebooks, laptops, distributed systems, gaming consoles (e.g., Xbox,Play Station, Wii), watches, glasses, iBeacons, proximity beacons, keyfobs, RFID tags, ear pieces, scanners, cameras, wristbands, kiosks,input terminals, servers or server networks, blades, gateways, switches,processing devices, processing entities, set-top boxes, relays, routers,network access points, base stations, the like, and/or any combinationof devices or entities adapted to perform the functions, operations,and/or processes described herein. As shown in FIG. 3, the distributedcomputing entity 110 may include an antenna 312, a transmitter 304(e.g., radio), a receiver 306 (e.g., radio), and a processing element308 (e.g., CPLDs, microprocessors, multi-core processors, coprocessingentities, ASIPs, microcontrollers, and/or controllers) that providesignals to and receive signals from the transmitter 304 and receiver306, respectively.

The signals provided to and received from the transmitter 304 and thereceiver 306, respectively, may include signaling information/data inaccordance with air interface standards of applicable wireless systems.In this regard, the distributed computing entity 110 may be capable ofoperating with one or more air interface standards, communicationprotocols, modulation types, and access types. More particularly, thedistributed computing entity 110 may operate in accordance with any of anumber of wireless communication standards and protocols, such as thosedescribed above with regard to the occupancy computing entity 100. In aparticular embodiment, the distributed computing entity 110 may operatein accordance with multiple wireless communication standards andprotocols, such as UMTS, CDMA2000, 1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN,EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IR, NFC, Bluetooth, USB, Wibree,HomeRF, SWAP, and/or the like. Similarly, the distributed computingentity 110 may operate in accordance with multiple wired communicationstandards and protocols, such as those described above with regard tothe occupancy computing entity 100 via a network interface 320.

Via these communication standards and protocols, the distributedcomputing entity 110 can communicate with various other entities usingconcepts such as Unstructured Supplementary Service Data (USSD), ShortMessage Service (SMS), Multimedia Messaging Service (MMS), Dual-ToneMulti-Frequency Signaling (DTMF), and/or Subscriber Identity ModuleDialer (SIM dialer). The distributed computing entity 110 can alsodownload changes, add-ons, and updates, for instance, to its firmware,software (e.g., including executable instructions, applications, programmodules), and operating system.

According to one embodiment, the distributed computing entity 110 mayinclude a location determining aspect, device, module, functionality,and/or similar words used herein interchangeably. For example, thedistributed computing entity 110 may include outdoor positioningaspects, such as a location module adapted to acquire, for example,latitude, longitude, altitude, geocode, course, direction, heading,speed, universal time (UTC), date, and/or various otherinformation/data. In one embodiment, the location module can acquireinformation/data, sometimes known as ephemeris data, by identifying thenumber of satellites in view and the relative positions of thosesatellites (e.g., using GPS). The satellites may be a variety ofdifferent satellite systems, including LEO satellite systems, DODsatellite systems, the European Union Galileo positioning systems, theChinese Compass navigation systems, Indian Regional Navigationalsatellite systems, and/or the like. This information/data can becollected using a variety of coordinate systems, such as the DD; DMS;UTM; UPS coordinate systems; and/or the like. Alternatively, thelocation information/data can be determined/identified by triangulatingthe distributed computing entity's 110 position in connection with avariety of other systems, including cellular towers, Wi-Fi accesspoints, and/or the like. Similarly, the distributed computing entity 110may include indoor positioning aspects, such as a location moduleadapted to acquire, for example, latitude, longitude, altitude, geocode,course, direction, heading, speed, time, date, and/or various otherinformation/data. Some of the indoor systems may use various position orlocation technologies including RFID tags, indoor beacons ortransmitters, Wi-Fi access points, cellular towers, nearby computingdevices (e.g., smartphones, laptops) and/or the like. For instance, suchtechnologies may include the iBeacons, Gimbal proximity beacons,Bluetooth Low Energy (BLE) transmitters, NFC transmitters, and/or thelike. These indoor positioning aspects can be used in a variety ofsettings to determine/identify the location of someone or something towithin inches or centimeters.

The distributed computing entity 110 may also comprise a user interface(that can include a display 316 coupled to a processing element 308)and/or a user input/interaction interface (coupled to a processingelement 308). For example, the user interface may be a user application,browser, user interface, and/or similar words used hereininterchangeably executing on and/or accessible via the distributedcomputing entity 110 to interact with and/or cause display ofinformation/data from the occupancy computing entity 100, as describedherein. The user input/interaction interface can comprise any of anumber of devices allowing the distributed computing entity 110 toreceive information/data, such as a keypad 318 (hard or soft), a touchdisplay, voice/speech or motion interfaces, or other input device. Inembodiments including a keypad 318, the keypad 318 can include (or causedisplay of) the conventional numeric (0-9) and related keys (#, *), andother keys used for operating the distributed computing entity 110 andmay include a full set of alphabetic keys or set of keys that may beactivated to provide a full set of alphanumeric keys. In addition toproviding input, the user input/interaction interface can be used, forexample, to activate or deactivate certain functions, such as screensavers and/or sleep modes.

The distributed computing entity 110 can also include volatile storageor memory 322 and/or non-volatile storage or memory 324, which can beembedded and/or may be removable. For example, the non-volatile memorymay be ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards,Memory Sticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM,Millipede memory, racetrack memory, and/or the like. The volatile memorymay be RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM,cache memory, register memory, and/or the like. The volatile andnon-volatile storage or memory can store databases, database instances,database management systems, data, applications, programs, programmodules, scripts, source code, object code, byte code, compiled code,interpreted code, machine code, executable instructions, and/or the liketo implement the functions of the distributed computing entity 110. Asindicated, this may include a user application that is resident on theentity or accessible through a browser or other user interface forcommunicating with the occupancy computing entity 100, and/or variousother computing entities.

In another embodiment, the distributed computing entity 110 may includeone or more components or functionalities that are the same or similarto those of the occupancy computing entity 100, as described in greaterdetail above. As will be recognized, these architectures anddescriptions are provided for exemplary purposes only and are notlimited to the various embodiments.

In one embodiment, distributed computing entities 110 may be fixed withregard to their geographic locations, such as by being in fixedpositions at apartment buildings, condominium buildings, officebuildings, industrial parks, and/or the like. In another embodiment,distributed computing entities 110 may be mobile with regard to theirgeographic locations. For example, one or more of the distributedcomputing entities 110 may be handheld devices carried by individuals(e.g., smartphones), handheld devices carried by carrier personnel,mobile devices secured relative to delivery vehicles, and/or the like.As will be recognized, a variety of other approaches and techniques canbe used to adapt to various needs and circumstances.

5. Exemplary Service Point Device

Example embodiments provide for interaction with a service point device117 using wireless communication interfaces as discussed in copendingU.S. patent application Ser. No. 15/349,189, which is incorporatedherein by reference in its entirety. In particular, the service pointdevice 117 may be an electronic and/or computing device physicallylocated at the service point and/or in and/or affixed to a building orstructure located at the service point. Some examples of a service pointdevice 117 include an electronic doorbell (e.g., a Ring.com® doorbell),beacon, storage locker, electronic mailbox, IOT enabled device (e.g., athermostat (e.g., a Nest® Thermostat, an Ecobee® Thermostat, and/or thelike), IOT enabled garage door opener, IOT enabled door lock, IOTenabled light bulb, and/or the like), and/or the like. For example, inone embodiment, the service point device 117 is an interactive,electronic, or “smart” doorbell affixed to the exterior of a residentialor commercial unit (e.g., an apartment, office, condominium, and/or thelike).

In example embodiments, a service point device 117 may include one ormore components that are functionally similar to those of the occupancycomputing entity 100, the distributed computing entity 110, usercomputing entity 120, and/or the like. FIG. 4 provides a block diagramof an example service point device 117. For example, a service pointdevice 117 may comprise a processor 150, a memory 152 (e.g., volatileand/or non-volatile memory), one more communication interfaces 154,and/or the like. As with other entities, the service point device 117may include one or more imaging devices 158 (e.g., video cameras and/orstill cameras) to capture image data (e.g., pictures, video, and/or thelike). The service point device 117 may also include one or moreactivity or motion detection sensors 156 or capabilities for zones ofinterest, such as Light Detection and Ranging (LIDAR) sensors,laser-based distance sensors, infrared distance sensors, ultrasonicdistance sensors, and/or the like. Moreover, one or more sensor arrays156 may be configured to detect motion and trigger the imaging devicesto collect, capture, and/or store image data.

Additionally, the service point device 117 may be configured tocommunicate with one or more other computing entities (e.g., distributedcomputing entity 110, user computing entity 120, and/or the like) viaone or more wired or wireless networks (e.g., through a communicationinterface 154). The service point device 117 may further comprise acommunications interface 154 configured to communicate with one or moreother computing entities (e.g., user computing entity 120, item/shipment102, delivery vehicle 107, and/or the like) using a short/long rangecommunication technology (e.g., Bluetooth technology, Bluetooth lowenergy technology, near field communication (NFC) technology, RFIDtechnology, Wi-Fi technology, ZigBee technology, infrared technology,ultra-wideband technology), and/or any other suitable communicationtechniques, standards, or protocols. For example, a communicationsinterface 154 may be in communication with one or more antenna 155configured to receive and/or transmit short/long range communications.

In certain embodiments, the service point device 117 may be in networkcommunication with one or more user computing entities 120 associatedwith entity (e.g., resident/occupant). The service point device 117 maybe configured to detect whether the user computing entity 120 associatedwith the entity is nearby (e.g., within a wireless communication rangeof the service point device 117), such that the service point device 117is configured to detect the presence of the user computing entity 120.In certain embodiments, the service point device 117 may be configuredto correlate the detection of the user computing entity 120 with thepresence of the associated entity (e.g., resident) at theunit/address/service point associated with the service point device 117.In such embodiments, the service point device 117 may be configured toprovide real-time entity status information/data to an occupancycomputing entity 100 indicative of whether the entity is located at theunit/address/service point, as discussed in greater detail herein.

In example embodiments, the service point device 117 may comprise anexterior interface 160 and/or comprise and/or be in communication withan interior interface 162. In example embodiments, the exteriorinterface 160 is located on the exterior of the building or structurelocated at the service point. In example embodiments, if the servicepoint device 117 is affixed to a building or structure, the exteriorinterface 160 may be located in the vicinity of the service point device117 on the exterior of the building or structure. The interior interface162 may be located anywhere within the building that the service pointdevice 117 is affixed to and/or associated with. In an exampleembodiment, the interior interface 162 is secured to an interior wall ofthe building that the service point device 117 is affixed to and/orassociated with. In another example embodiment, the interior interface162 is configured to be moved from room-to-room within the building thatthe service point device 117 is affixed to and/or associated with. Theinterior and/or exterior interfaces 160, 162 may comprise one or morespeakers or other components configured for producing an audible signal;a keypad (soft or hard) comprising one or more press-able, selectable,and/or otherwise interactive buttons/keys; a display (e.g., configuredfor displaying at least notifications and/or pictures, video, and/or thelike captured by the one or more imaging devices 158 of the servicepoint device 117), and/or the like. In example embodiments, theprocessor 150 may be in communication with the interior interface 162via a short/long range communication technology, a wired and/or wirelessnetwork, or through a direct wired (e.g., USB, Ethernet, or other datacable) or wireless connection. In some embodiments, the interiorinterface 162 may be functionally coupled to the processor 150, and/ormay be operated by a processing element dedicated to the interiorinterface 162. As will be recognized, these architectures anddescriptions are provided for exemplary purposes only and are notlimited to the various embodiments.

6. Exemplary User Computing Entity

In one embodiment, a user computing entity 120 may be operated bycarrier/transporter personnel/operator (e.g., picking up and/ordelivering items/shipments to customers). The user computing entity 120may be a handheld/mobile computing entity, such as a PDA, a smart phone,an autonomous vehicle, and/or the like. In one embodiment, a usercomputing entity 120 may include one or more components that arefunctionally similar to those of the occupancy computing entity 100, thedistributed computing entity 110, and/or the like. For example, in oneembodiment, each user computing entity 120 may include one or moreprocessing elements (e.g., CPLDs, microprocessors, multi-coreprocessors, coprocessing entities, ASIPs, microcontrollers, and/orcontrollers), one or more display device/input devices (e.g., includinguser interfaces), volatile and non-volatile storage or memory, and/orone or more communications interfaces. For example, the user interfacemay be a user application, browser, user interface, interface, and/orsimilar words used herein interchangeably executing on and/or accessiblevia the user computing entity 120 to interact with and/or cause displayof information, as described herein. This may also enable the usercomputing entity 120 to communicate with various other computingentities, such as carrier/transporter computing entities, distributedcomputing entities 110, and/or various other computing entities. As willbe recognized, these architectures and descriptions are provided forexemplary purposes only and are not limited to the various embodiments.

7. Exemplary Distributed Ledger System (e.g., Blockchain)

In certain embodiments, a distributed ledger system may storeinformation/data indicative of various transactions occurring betweenmultiple computing entities (e.g., multiple transaction computingentities). The distributed ledger system may be embodied as a blockchainledger system, comprising a plurality of “blocks” each representing adiscrete transaction occurring between computing entities. Each blockmay comprise information/data linking to a previous generated block,thereby providing a complete chain between the generation ofinformation/data stored in the distributed ledger and the later use ofthe same information/data (e.g., to establish a completechain-of-possession of information/data). The distributed ledger systemmay comprise one or more Ethereum-based blockchains, Hyperledgerblockchains, and/or the like. The distributed ledger system mayincorporate a single blockchain configured for storing all transactionstherein, or the distributed ledger system may comprise a plurality ofblockchains, wherein each blockchain is utilized to storeinformation/data indicative of a particular type of transaction. Forexample, a first blockchain may be configured to store parcel trackinginformation/data, and a second blockchain may be configured to storevalue transfer information/data (e.g., via a virtual currency).

The distributed ledger system may be stored in and/or by one or morecomputing entities (e.g., occupancy computing entity 100) in complete orpartial form. For example, each of a plurality of computing entities maystore a complete copy of the one or more blockchains, and may beutilized for backup protection and/or transaction verification purposes.The distributed ledger system may be publicly accessible, and may bedistributed among a plurality of commercial computing entities (e.g.,servers), user computing entities (e.g., desktop computers, laptopcomputers, and/or the like), and/or the like. However, in certainembodiments, the distributed ledger system may be privately accessible,and may be stored by one or more computing entities controlled by asingle entity. In the latter embodiments, access to information/datastored in the distributed ledger may be limited to users having definedcredentials (e.g., a private key, a passcode, and/or the like). Incertain embodiments, information/data stored in the distributed ledgersystem may be hashed, encrypted, or otherwise protected fromunauthorized access (e.g., read access and/or write access). Thesubstantive information/data stored in the distributed ledger system maybe accessible utilizing a private key to decrypt the storedinformation/data, or the substantive information/data may beinaccessible based on information/data stored in the distributed ledger.

In various embodiments, each block of a blockchain stored in thedistributed ledger may comprise location-identifying information/dataand/or entity identifying information/data (e.g., occupancyinformation/data for a particular entity), and may represent a movingevent for the corresponding entity. For example, each time an entitychanges occupancy from one location to another, the distributed ledgersystem may be configured to generate a new block providinginformation/data indicative of the transaction. In certain embodiments,each block may comprise at least a portion of the entityinformation/data, thereby providing a link back to a prior blockrepresenting a transaction involving the same entity information/data.

IV. Exemplary System Operation

As noted above, various embodiments are directed to the implementationand/or maintenance of an occupancy database comprising occupancyinformation/data for a plurality of entities within a plurality of units(e.g., apartments, condominiums, houses, offices, and/or the like). Theoccupancy database may be in communication with a plurality ofdistributed computing entities 110, thereby forming an automaticallyupdating system for maintaining real-time (or near real-time) occupancyinformation/data that is self-verified based on information/dataaccessible via at least a subset of the distributed computing entities110.

The self-updating occupancy system (including the occupancy database),may comprise information/data regarding the current status of variousentities relative to corresponding units/addresses/service points (e.g.,available/unavailable information/data), connectivity information/datafor various service point devices at the correspondingunits/addresses/service points, and/or the like. The storedinformation/data may be available to various user computing entities 120such as those carried by carrier delivery personnel, therebyfacilitating connectivity between the user computing entity 120 andvarious computing entities at the corresponding units/addresses/servicepoints of an entity. In certain embodiments, the information/dataaccessible to the user computing entities may facilitate delivery ofvarious shipments/items 102. For example, through connectivity withvarious service point devices at a particular unit/address/service point(as facilitated by information/data stored in the occupancy database),various embodiments may enable automated electronic deliveryconfirmation signatures, electronic delivery attempt notifications,and/or the like to be implemented during delivery as discussed inco-pending U.S. patent application Ser. No. 15/349,189, filed on Nov.11, 2016 and which is incorporated herein by reference in its entirety.

1. Service Points

In example embodiments, a service point may be a delivery location,pick-up location, or other location at which a delivery vehicle and/ordriver are to provide a service on behalf of the carrier. In oneembodiment, a “service point” may be any identifiable location, such asone or more addresses, delivery locations, parking locations, sidewalks,highways, trails, alleys, paths, walkways, streets, street segments,entrance or exit ramps, roads, longitude and latitude points, geocodes,zip codes, area codes, territories, cities, counties, states, provinces,countries, stops (e.g., pick up stops, delivery stops, vehicle visits,stops), geofenced areas, geographic areas, landmarks, buildings,bridges, and/or other identifiable locations. For example, a servicepoint may be a residential location, such as one or more homes, one ormore mobile homes, one or more apartments, one or more apartmentbuildings, one or more condominiums, one or more townhomes, one or morepoints at such locations, and/or the like. The service point may also beany specific location at a residential location, e.g., (e.g., front doorof a residence, side door of a residence, and/or the like). A servicepoint may also be a commercial location, such as one or more stores in amall, one or more office buildings, one or more office parks, one ormore offices of an apartment complex, one or more garages, one or morewarehouses, one or more restaurants, one or more stores, one or moreretail locations, one or more points at such locations, and/or the like.The service point may also be any specific location at a commerciallocation, e.g., (e.g., front door of a commercial location, dock of acommercial location, and/or the like). A service point may be one ormore streets, one or more street segments, one or more zones, one ormore areas, one or more latitude and/or longitude points (e.g.,33.7869128, −84.3875602), one or more geocodes, and/or the like. Aservice point may be any identifiable location. As will be recognized, avariety of approaches and techniques can be used to adapt to variousneeds and circumstances.

2. Exemplary Occupancy Database

The occupancy database may be embodied as a storage memory in electroniccommunication with the occupancy computing entity 100. The occupancydatabase may be maintained publicly by a single entity (e.g., a carrier,a government agency, and/or the like), a distributed plurality ofentities (e.g., as a distributed ledger or blockchain), and/or the like.In other embodiments, the occupancy database may be maintained privatelyby a single entity (e.g., an apartment building management company, acarrier, an identity verification company, and/or the like) or adistributed consortium of entities (e.g., a plurality of carriers, aplurality of private companies, and/or the like). Accordingly, theoccupancy database may be associated with a single location (e.g., asingle apartment building) or the occupancy database may be associatedwith a plurality of locations. Moreover, the occupancy database may beembodied as a centrally stored and managed database (e.g., within localmemory of the occupancy computing entity 100, or within local serversassociated with the occupancy computing entity 100), as a cloud-baseddatabase (e.g., stored within external, network-connected storagedevices), as a distributed database (e.g., stored on a plurality ofnetwork-connected storage devices), and/or the like.

In certain embodiments, at least portions of the occupancy database maybe downloaded (e.g., temporarily downloaded) onto a user computingentity 120 and/or a distributed computing entity 110. For example,selected entity profiles (described in greater detail herein) may bedownloaded onto a user computing entity 120 corresponding to anitem/shipment delivery personnel and/or autonomous delivery vehicle suchthat occupancy information/data corresponding to upcoming item/shipmentdeliveries may be easily accessible via local memory of the usercomputing entity 120.

As discussed herein, the information/data stored within the occupancydatabase may be available via a network (e.g., the internet), and thusany of a variety of network connected computing entities may beconfigured to access information/data stored within the occupancydatabase. In certain embodiments, the information/data stored within theoccupancy database may be stored using a unique or proprietary filetype, storage organization, and/or the like, and accordingly the storedinformation/data may be available to computing entities operatingspecially configured computing programs (e.g., standalone computingprograms and/or multi-function computing programs incorporatingoccupancy database accessibility therein) configured to read and/orexecute information/data stored within the occupancy database. However,the information/data stored within the occupancy database according tovarious embodiments may be stored in browser-executable file types, suchas HTML, HTML5, PHP, and/or the like, and may therefore be accessiblevia any of a variety of computing entities via a browser programdirected to a web-based interface (e.g., hosted by the occupancycomputing entity 100).

In certain embodiments, various computing entities (e.g., distributedcomputing entities 110, user computing entities 120, and/or the like)may be configured to access various portions of the occupancy data toenable users to review and/or update various portions ofinformation/data stored within the occupancy database. For example,users may be enabled to access (e.g., read/write access) stored entityprofiles comprising information/data about themselves, while carriercomputing entities may be configured to access (e.g., read-only access)information/data regarding a plurality of entity profiles.

The information/data stored in the occupancy database may be organizedinto a plurality of entity profiles each corresponding to a particularentity (e.g., a business, an individual, a family, and/or the like).FIG. 4 illustrates example information/data stored in an entity profilecorresponding to a fictional individual named John Doe. As shown in FIG.4, the entity profile may comprise information/data identifying acurrent residence/shipping address of the corresponding entity (e.g.,street address, including unit number, if applicable; P.O. Box address,and/or the like). Although not shown, the entity profile may compriseinformation/data corresponding to a plurality of currentresidences/shipping addresses for the entity (e.g., including a primaryresidence and/or a plurality of secondary residences).

Moreover, as shown in FIG. 4, the entity profile may compriseinformation/data identifying a plurality of historical addressescorresponding to the entity. These historical addresses may be stored asunique entries in an individually stored entity profile, or thehistorical address information/data may be stored in a plurality ofprevious-in-time generated blocks in a blockchain based occupancydatabase. In the latter exemplary embodiments, historical addressinformation/data need not be individually stored and/or maintainedwithin the occupancy database, but instead may be accessed as needed byretrieving information/data stored in a prior-generated block. Asdiscussed in greater detail herein, the occupancy database may beconfigured to automatically move a “current” address corresponding to anentity to the “previous” address portion of the entity profile upon adetermination that the entity has updated a current addressinformation/data stored in the entity profile.

As shown in FIG. 4, the entity profile may comprise additionalinformation/data corresponding to a particular entity. For example, theentity profile may comprise contact information/data for the entity(e.g., phone number, social network contact information, email address,and/or the like). The entity profile may additionally compriseconnection information/data that may be used to establish a wirelessdata connection with one or more service point devices 117 located atone or more addresses corresponding to the entity. The connectioninformation/data may comprise one or more executable programs that maybe utilized by an accessing computing entity (e.g., a user computingentity 120) without additional user input by a user of the accessingcomputing entity. Thus, upon being brought within a connectivity rangeassociated with the serviceable point device 117 (which may bedetermined based on the wireless transmission protocol utilized by theserviceable point device 117), the accessing computing entity may beconfigured to automatically establish a wireless data communicationinterface with the serviceable point device 117. As yet other examples,the connection information/data may comprise information/dataidentifying a type of communication protocol utilized by the serviceablepoint device 117, and one or more passphrases, virtual handshakeinformation, validation criteria, and/or the like utilized by theserviceable point device 117 to establish connection therewith. A usercomputing entity 120 accessing the entity profile may be configured toexecute one or more locally stored computing programs to utilize theconnection information/data to establish a wireless connection interfacewith the serviceable point device 117 once available. Via the locallystored computing program, the user computing entity 120 may beconfigured to determine an expected communication range for theserviceable point device 117 based on connection information/data storedin the entity profile. Upon detecting that the user computing entity 120is within the expected communication range for the serviceable pointdevice 117, the user computing entity 120 may begin searching forwireless connectivity signals transmitted by the serviceable pointdevice 117 (e.g., the user computing entity 120 may enter a listeningmode to listen for signals generated by the serviceable point device117, and/or the user computing entity may generate and transmit one ormore ping signals to the serviceable point device 117). Upon detectingthe serviceable point device 117, the user computing entity 120 mayinitiate establishing a wireless communication interface using theauthorization credentials stored in the entity profile. Thereafter, theuser computing entity 120 may transmit and/or receive information/datawith the serviceable point device 117, as discussed in greater detailherein.

With reference again to FIG. 4, the entity profile may additionallyinclude status information/data for the entity. The statusinformation/data may indicate whether the entity is available to acceptdelivery of an item/shipment 102 (e.g., whether an individual associatedwith the entity is located at the current address associated with theentity to accept delivery of the item/shipment 102). In certainembodiments, the status information/data may be generated by one or moreof the serviceable point devices 117 (e.g., based on wirelessconnectivity status with user computing entities 120 carried byindividuals associated with the entity), and may be transmitted to theoccupancy computing entity 100 (e.g., via one or more distributedcomputing entities 110 in communication with the serviceable pointdevices 117) in real-time or near real-time to maintain accurate andcurrent status information/data for the entity profile. As noted above,the service point devices 117 may be configured to wirelesslycommunicate with various user computing entities 120 associated with anoccupant/resident/entity associated with the serviceable point. Upondetecting the presence of the user computing entity 120 (e.g., based onan established wireless communication interface between the servicepoint device 117 and the user computing entity 120), the service pointdevice 117 may be configured to transmit (in real-time or nearreal-time) status information/data indicating the presence of theentity. Thus, the establishment or loss of a wireless communicationinterface between the service point device 117 and a user computingentity may be a trigger event for the service point device 117 totransmit updated status information/data to the occupancy computingentity 100. For example, upon establishing a wireless communication linkwith an entity's user computing entity 120, the service point device 117may transmit updated status information/data to the occupancy computingentity 100 indicating the entity is available at theunit/address/service point. Likewise, upon detecting a loss of wirelessconnectivity with the entity's user computing entity 120 (e.g., upon theuser computing entity 120 leaving a wireless communication range withthe service point device 117), the service point device 117 may beconfigured to transmit updated availability information/data to theoccupancy computing entity 100 indicating the entity is unavailable atthe unit/address/service point.

In certain embodiments, the entity profile may additionally compriseservice provider preferences established by the entity associated withthe entity profile. As one non-limiting example, the service providerpreferences may comprise delivery preferences for item/shipmentdeliveries to be made to an address associated with the entity profile.These delivery preferences may be provided by an entity associated withthe entity profile (e.g., via user input provided to a distributedcomputing entity 110 and transmitted to the occupancy computing entity100), and may establish preferences such as “leave at” instructions forleaving an item/shipment 102 at the address, redirect instructions fordelivering an item/shipment 102 to an alternative location if deliveryto the address included in the entity profile is not possible.

In various embodiments, the information/data stored within the entityprofile may be encrypted (e.g., using a private and/or public key),hashed, and/or otherwise secured against unauthorized access to thestored information/data. In such embodiments computing entities (e.g.,user computing entities 120, distributed computing entities, occupancycomputing entity 100, and/or the like) may store an encryption key,hashing algorithm, and/or the like configured to enable the computingentity to retrieve information/data from the entity profile and/or toverify information/data against that information/data stored in theentity profile.

In certain embodiments, at least portions of the information/data storedin the occupancy database may be linked with a carrier-specific addressdatabase and/or item/shipment database for various users and/oritems/shipments 102, and/or with a carrier loyalty program that providesusers with the ability to provide carrier-specific instructions forvarious items/shipments 102 to be delivered to those users. In suchembodiments, the carrier-specific address database (or othercarrier-specific database) may be maintained by the carrier, and may beconfigured to cross-link information/data stored in the occupancydatabase. In certain embodiments, the carrier address database may beprovided with read-only information/data access to at least a portion ofthe occupancy database (e.g., at least those entity profilescorresponding to user/address profiles stored in the carrier addressdatabase). However, in certain embodiments the carrier address databasemay have read/write access to the occupancy database, such thatinformation/data stored within the carrier address database may beutilized to maintain up-to-date information/data stored in the occupancydatabase.

When linked with a carrier address database (or other carrier-specificsystems), the information/data stored in the occupancy database may beutilized to supplement delivery information/data for shipments/items 102destined for various entities. For example, the carrier address databasemay comprise information/data corresponding to future and/or in-transitshipments/items 102 destined for various entities. In such embodiments,the carrier address database may (e.g., via a distributed computingentity 110) verify that address information/data for each item/shipment102 is correct and complete. Upon determining that addressinformation/data for a particular item/shipment 102 is incomplete, thecarrier address database may supplement the address information/data forthe item/shipment 102 to provide a complete address to facilitate finaldelivery of the item/shipment 102.

To verify address information/data corresponding to a particularitem/shipment 102, the carrier address database may generate a query tothe occupancy database comprising identifying information for aparticular destination location associated with the item/shipment 102.For example, the carrier address database may provide a uniquecombination of recipient name, recipient street name, recipient streetnumber, recipient city, recipient state, recipient country, recipientzip/postal code, recipient user name, recipient social security number,and/or the like. The carrier address database need not provide completeaddress information/data (e.g., the provided information/data may bemissing a unit number, may have an incorrectly spelled street name,and/or the like), but need only provide sufficient information/data toidentify the recipient of the item/shipment 102. The occupancy computingentity 100 may receive the generated query, and may retrieve acorresponding entity profile from the occupancy database correspondingto the unique combination of information/data provided by the carrieraddress database. The occupancy computing entity 100 may then generateand transmit a response to the carrier address database indicative of acorrect destination address for the particular item/shipment 102. Theresponse may identify errors and/or omissions in the information/dataprovided by the carrier address database, and the carrier addressdatabase may be configured to update the shipping information/data forthe item/shipment 102 to reflect the correct and complete addressinformation/data. In certain embodiments, the corrected addressinformation/data provided by the occupancy computing entity 100 mayreflect an entirely new address for the entity, for example, upondetermining that the item/shipment recipient has moved away from anaddress provided by the carrier address database and to a new address.Accordingly, the carrier address database may be configured toautomatically redirect/forward shipments/items 102 to an updated addresscorresponding to an item/shipment recipient based at least in part oninformation/data received from the occupancy computing entity 100.

The occupancy information/data stored in the occupancy database may bemaintained as up-to-date in real-time or near real-time based on updatedoccupancy information/data received from one or more distributedcomputing entities 110. The distributed computing entities 110, whichmay comprise property management computing entities (e.g., apartmentmanagement computing entities, condominium management computingentities, office building management computing entities, and/or thelike), municipal property records computing entities, user computingentities, third party computing entities (e.g., computing entitiesmaintained by the United States Postal Service), and/or the like, may belocation specific and may correspond to a single property, or maycorrespond to a plurality of properties in a particular area. Theplurality of distributed computing entities 110 collectively define anetwork of computing entities maintaining occupancy information/data fora plurality of entities at various locations. Each of these plurality ofdistributed computing entities may provide updated occupancyinformation/data (e.g., comprising information/data indicative of alocation change for the entity and/or an effective date for the locationchange) to the occupancy database regularly, periodically, and/or as newinformation/data is generated. For example, various location-specificdistributed computing entities 110 may be configured to generate newoccupancy information/data as new residents, occupants, and/or the likemove into the location corresponding to the particular distributedcomputing entity 110. As a specific example, for a distributed computingentity 110 embodied as an apartment complex management computing entity,the distributed computing entity 110 may be configured to receive newoccupancy information/data whenever a new resident joins the apartmentcomplex. The distributed computing entity 110 may thus be configured tocompile occupancy information/data regarding those new residents (in aformat acceptable to the occupancy database), and may transmit theoccupancy information/data to the occupancy database. In certainembodiments, the distributed computing entities may be configured totransmit the information/data to the occupancy database through anapplication programming interface (API) to ensure information/data isappropriately provided to the occupancy database. However, it should beunderstood that the information/data may be provided from the variousdistributed computing entities 110 to the occupancy database via any ofa variety of information/data exchanges.

As yet another example, for distributed computing entities 110 embodiedas municipal property management computing systems, new occupancyinformation/data may be generated and/or transmitted to the occupancydatabase upon receipt of information/data indicating that a piece ofproperty tracked by the municipal property management computing systemhas been transferred, leased, and/or the like. In such embodiments, thedistributed computing entity 110 may transmit occupancy information/datato the occupancy database in a format acceptable to the occupancydatabase in a manner similar to that discussed above.

As another specific example, for a distributed computing entity 110embodied as a USPS controlled computing entity, new occupancyinformation/data may be generated and/or transmitted to the occupancydatabase upon receipt of mail forwarding information/data at the USPSfor a particular entity. For example, after an individual submits a mailforwarding request to reflect a chance in residence, data indicative ofthe changing residence information/data may be transmitted/provided tothe occupancy database for storage with the entity profile correspondingto the individual. Such information/data may also comprise an effectivedate for the change in occupancy for the individual submitting theforwarding request.

As yet another example, distributed computing entities 110 and/or usercomputing entities 120 corresponding to individual entities may beutilized to update and/or generate new occupancy information/data forthose individual entities. For example, individual entities may provideupdated occupancy information/data (e.g., via user input) through a userinterface configured to provide updated occupancy information/data tothe occupancy database.

The occupancy database may comprise aspects for verifying occupancyinformation/data provided to the occupancy database. These verificationaspects may be embodied as computer program portions stored in theoccupancy database and operable by the occupancy computing entity 100 todirect the operation of a plurality of computing entities (including theoccupancy computing entity 100 and one or more distributed computingentities 110). Because the location-specific distributed computingentities 110 may, in certain embodiments, comprise the most up-to-dateinformation/data concerning the occupancy of various entities, theverification computing programs may utilize information/data stored in avariety of distributed computing entities 110 to verify information/datastored on the occupancy database. The occupancy computing entity 100 maybe configured to verify occupancy information/data once received, andbefore updating the occupancy database to reflect the newly receivedoccupancy information/data.

FIG. 6 is a flowchart illustrating example steps for verifying occupancyinformation/data for a particular entity. As mentioned, new and/orupdated occupancy information/data may be generated and transmitted fromvarious distributed computing entities 110, for example, when entitiesbecome associated with a new distributed computing entity 110 (e.g.,when an entity joins a new building, complex and/or the like managed bya single distributed computing entity 110). The new and/or updatedoccupancy information/data may be transmitted to the occupancy computingentity 100 from a distributed computing entity 110 associated with thenew occupancy location for storage in the occupancy database. Receipt ofthe new and/or updated occupancy information/data by the occupancycomputing entity 100 (as indicated at Block 601) may trigger initiationof the verification process of the occupancy computing entity 100.

The verification process may begin by identifying relevant portions ofthe new and/or updated occupancy information/data that may be utilizedto generate a query to the occupancy database to retrieve acorresponding entity profile for the entity associated with the newoccupancy information/data, as indicated at Block 602 of FIG. 6. Forexample, if the updated occupancy information/data indicates that aparticular resident has moved into a new apartment building, theverification process may be configured to identify information/datawithin the updated occupancy information/data that may be utilized toidentify an existing entity profile corresponding to the new resident(e.g., name, prior address information, social security number, and/orthe like). The occupancy computing entity 100 may then retrieve thecorresponding entity profile for the entity, to retrieveinformation/data regarding the previously identified current occupancyinformation/data for the entity as indicated at Block 603. Referring tothe previous example, once the entity profile is retrieved for the newapartment resident, the occupancy computing entity 100 identifies storedoccupancy information/data within the entity profile identifying thecurrent residence of the new resident as identified in the entityprofile. Because the entity profile has not yet been updated to reflectthe resident's recent move to the new apartment building, the storedoccupancy information/data of the entity profile indicates that theresident still resides at the resident's prior apartment.

The verification process continues by identifying a distributedcomputing entity 110 associated with the entity's prior stored occupancyinformation/data (e.g., a resident's prior apartment building). Theoccupancy computing entity 100 may be configured to review metadatastored with the prior occupancy information/data, or to identify otherinformation/data stored within the occupancy database that may beutilized to identify a distributed computing entity 110 associated withthe entity's prior occupancy information/data. With reference again tothe new-resident example above, the occupancy computing entity 100 maybe configured to identify an apartment management computing entityassociated with the resident's prior apartment building (e.g., theapartment management computing entity that provided the previous updateinformation/data to the occupancy computing entity 100 for theresident).

The occupancy computing entity 100 may then generate and transmit aquery to the identified distributed computing entity 110 associated withprior occupancy information/data to determine whether the identifiedentity has vacated a unit/address/service point associated with theprior distributed computing entity 110, as indicated at Block 604. Forexample, the occupancy computing entity 100 may generate and transmit aquery to the resident's prior apartment management computing entity todetermine whether the resident has vacated and/or will vacate anapartment at the previous building. The distributed computing entity 110may then provide information/data to the occupancy computing entity 100indicating whether the resident has vacated the prior apartment, hasprovided written notice of an intent to vacate, and/or the like, asindicated at Block 605.

Upon receipt of information/data from the identified distributedcomputing entity 110 associated with prior occupancy information/datafor the entity, the occupancy computing entity 100 may be configured toverify the newly provided updated occupancy information/data and mayupdate the corresponding entity profile for the entity to reflect thenew occupancy information/data, as shown at Block 608. The occupancycomputing entity 100 may additionally move the previously identifiedcurrent/stored occupancy information/data in the entity profile to theprior-occupancy information/data portion of the entity profile. Thus, inthe prior example, once the occupancy computing entity 100 receives theverification information/data from the identified distributed computingentity 110 associated with the resident's prior apartment complex, theoccupancy computing entity 100 may update the resident's entity profileto reflect the new apartment building as the resident's current abode,and to reflect the prior apartment complex as one of the resident'sprior addresses.

However, if the distributed computing entity 110 associated with theentity's prior occupancy does not provide verification information/data(e.g., the entity is still reflected as a current occupant of the priorlocation according to information/data stored at the distributedcomputing entity 110), the occupancy computing entity 100 may beconfigured to generate and transmit an alert notification to thedistributed computing entity 110 associated with the new occupancylocation. The alert notification may request additional information,such as automatically and/or manually generated information/dataindicating whether the new occupancy information/data reflects asecondary occupancy (e.g., a secondary home, a secondary businesslocation, and/or the like), whether the new occupancy information/datahas an expected overlap with a prior occupancy information/data, and/orthe like. The distributed computing entity 110 may be configured toaccept user input indicating manual overrides of the generated alertnotification, and/or may be configured to automatically generate aresponse to provide additional information/data in response to the alertnotification as indicated at Block 606. If additional information/datais provided to override the alert notification (e.g., upon generation ofa secondary occupancy indicator), the occupancy computing entity 100 mayupdate the occupant profile as indicated at Block 609. If thedistributed computing entity 110 associated with the new occupancyinformation/data does not provide additional information/data inresponse to the alert notification, the occupancy computing entity 100may reject the proposed updated occupancy information/data and may notupdate the corresponding entity profile, as indicated at Block 607.

3. Registration

In example embodiments, an entity may register and/or establish anentity profile to be stored in the occupancy database. The entityprofile may be generated in response to affirmative action of the entityto provide information/data for the entity profile (e.g., via inputprovided to a user interface) and/or the entity profile may be generatedin response to a passive action on the part of the entity (e.g.,purchasing a home, leasing an apartment, leasing an office, purchasingan office building, and/or the like). The generated entity profile mayidentify an address corresponding with the entity (e.g., adelivery/pick-up address) at a particular service point. Moreover, uponregistration and generation of an entity profile, the entity profile maybe updated to include information/data indicative of various servicepoint devices 117 located at the service point.

In one embodiment, as part of the enrollment/registration process, thecustomer (e.g., operating a distributed computing entity 110) may berequested to provide biographic and/or geographic information/data bythe occupancy computing entity 100 (e.g., via a registration module).Such information/data may be manually input or provided by allowingaccess to other accounts, such as Facebook, Gmail, Twitter, PayPal,and/or the like. As yet other examples, such information/data may beprovided automatically, and may be populated based on information/dataprovided to a distributed computing entity 110 during the purchaseand/or lease process associated with a particular unit/address/servicepoint. For instance, the customer may provide the customer's name, suchas a first name, a last name, a company name, an entity name, and/or anorganization name. The customer (e.g., consignor or consignee) may alsoprovide any aliases associated with the customer. For instance, if thecustomer (e.g., consignor or consignee) were an individual named JosephBrown, the customer (e.g., consignor or consignee) may provide Joe Brownor Joey Brown as aliases.

In example embodiments, biographic and/or geographic information/datamay further comprise information/data relating to a service point device117 located at an address associated with the customer. For example, inaddition to providing the street address for a physical addressassociated with the customer, the customer may further provide anindication of whether the physical address is associated with a servicepoint device 117. For example, the customer may indicate that a servicepoint device 117 is located at the primary residential address of 100Main St Atlanta, Ga. 30309, USA. The customer may then provide anyinformation/data required for remote communication with the servicepoint device 117 located at the indicated address. For example, thecustomer may indicate one or more modes of communication by which theservice point device 117 is capable of communicating, an internetprotocol (IP) address associated with and/or assigned to the servicepoint device 117, a name associated with the service point device 117(e.g., Brown Family's doorbell), and/or other information/data needed tofacilitate remote communication with the service point device 117. Incertain embodiments, the information/data provided regarding the servicepoint device 117 may comprise one or more one-time-use connectivitypasswords associated with the service point device 117. In exampleembodiments, the customer may further provide preferences for use of theservice point device 117.

In one embodiment, once the occupancy computing entity 100 receives thenecessary biographic and/or geographic information/data from the entity,the occupancy computing entity 100 may perform one or more validationoperations. For example, the occupancy computing entity 100 maydetermine whether the primary address (and/or other addresses) in thespecified country or postal code is eligible for a customer pick-up,delivery, and/or returns programs. The occupancy computing entity 100may also determine whether the primary address (and/or other addresses)is valid, e.g., by passing the primary address through one or moreaddress cleansing and/or standardization systems. The occupancycomputing entity 100 may perform a variety of fraud prevention measuresas well, such as determining whether the entity (e.g., consignor orconsignee) or one of the entity's addresses has been “blacklisted” fromcustomer pick-up, delivery, and/or returns programs. As will berecognized, a variety of other approaches and techniques can be used toadapt to various needs and circumstances.

In one embodiment, the occupancy computing entity 100 may create acustomer profile for the customer via the enrollment/registrationprocess. Accordingly, the occupancy computing entity 100 may create andstore various customer profiles (e.g., via a database stored, forexample, in non-volatile memory 210). In addition to at least theinformation/data described above, a customer profile may include one ormore corresponding usernames and passwords. As will be recognized, eachof the physical addresses may be associated with the customer's profile.

In one embodiment, once a customer profile has been created by theoccupancy computing entity 100, the entity (e.g., operating adistributed computing entity 110) can provide various preferencesassociated with service calls to the entity's associated service pointto the occupancy computing entity 100 via an interface, for example. Forinstance, the entity (e.g., operating a distributed computing entity110) can provide a variety of preferences, such as communicationpreferences, service schedule preferences, delivery preferences,delivery options, delivery redirect options, remote activationpreferences, and/or delivery instructions. The entity (e.g., operating adistributed computing entity 110) may also update any information/datathrough the appropriate interface (e.g., browser, dashboard, webpage,application).

4. Identifying Relevant Occupancy Directory Entries

When utilizing and/or updating information/data stored in the occupancydatabase, various computing entities (e.g., distributed computingentities 110 and/or user computing entities 120) generate and transmitqueries to the occupancy computing entity 100 to retrieve relevantinformation/data from the connected occupancy database. The generatedqueries may reflect any of a variety of information/data types availableto the distributed computing entities 110 to accommodate any number ofpossible combinations of information/data identifying a particularoccupant. For example, the information/data utilized to generate a queryto the occupancy computing entity 100 may comprise an occupant name andat least part of a delivery address for the occupant. The partialdelivery address may comprise, for example, a street name, streetnumber, city name, state name, and zip code, but may omit a unit numberfor the occupant. Alternatively, the distributed computing entity 110may generate a query of the occupancy database comprising a particularentity's unique identifier (e.g., user name, social security number,password, and/or the like). Thus, the distributed computing entities 110may be configured to generate queries for the occupancy database basedon any of a variety of information/data types provided to thedistributed computing entity 110. For example, the distributed computingentity 110 may thus be configured to utilize shipping information/dataprovided for a particular item/shipment 102 to be delivered to theentity, or may utilize information/data provided by an entity whenpurchasing and/or leasing a property to generate a query of theoccupancy database.

The occupancy computing entity 100 may then retrieve an entity profilestored within the occupancy database that matches the information/dataprovided in the query from the distributed computing entity 110, and mayprovide at least a portion of the occupancy directory information/datato the distributed computing entity. The occupancy computing entity 100may be configured to utilize fuzzy matching logic when retrieving therelevant entity profile, to thereby accommodate potential typographicalerrors in the information/data provided in the query. For example, if adistributed computing entity 110 seeks information/data regarding JohnDoe, who lives at 123 Main Street, Atlanta, Ga. 30309 (as reflected inthe example entity profile shown in FIG. 5), the occupancy computingentity 100 may be configured to identify this same profile even if theprovided query requests information/data about Jon Doe, at 123 MaineStreet, Atlanta, Ga. 30309.

As mentioned above, user computing entities 120 and/or distributedcomputing entities 110 may be configured to download at least a portionof the occupancy information/data stored in the occupancy database. Incertain embodiments, the user computing entities 120 and/or distributedcomputing entities 110 may be configured to download select entityprofiles, for example, corresponding to queries provided by thosecomputing entities. As just one non-limiting example, a user computingentity 120 carried by an item/shipment delivery personnel may beconfigured to download and locally store entity profiles correspondingto item/shipment recipients for which the item/shipment deliverypersonnel is scheduled to deliver items/shipments during a particulardelivery route.

Various user computing entities 120 and/or distributed computingentities 110 may be configured to utilize information/data stored invarious entity profiles (e.g., downloaded and locally stored entityprofiles) to supplement address information/data for various entities.Referring to the above non-limiting example, the user computing entity120 corresponding to the delivery personnel may utilize information/datastored in the downloaded entity profiles to supplement delivery addressinformation/data for various items/shipments 102 to be delivered duringa particular delivery route. The user computing entity 120 maysupplement the delivery address information/data for variousitem/shipment deliveries by including additional information/dataregarding those item/shipment deliveries, such as missing unit numbersfor particular item/shipment recipients, precise delivery locationinformation/data (e.g., delivery to front door of unit/address/servicepoint or delivery to building concierge).

In embodiments in which a carrier address database is in communicationwith the occupancy database, the carrier address database may beconfigured to retrieve information/data stored in particular entityprofiles corresponding to items/shipments 102 to be delivered by carrierdelivery personnel. A computing entity associated with the carrieraddress database may be configured to retrieve complete and/orsupplemental address information/data corresponding to scheduleditem/shipment deliveries, and may generate updated delivery labels to begenerated and applied to the various items/shipments 102 to facilitatedelivery of those items/shipments 102 by delivery personnel. Forexample, the computing entity associated with the carrier addressdatabase may be configured to generate updated delivery labels upon adetermination that existing delivery labels comprise incomplete deliveryinformation/data for the corresponding shipments/items 102 (e.g.,missing unit numbers, and/or the like).

5. Enabling Communication between User Computing Entity and Occupant

The entity profiles for various entities may comprise contactinformation/data for those entities, and therefore various embodimentsmay enable communication between user computing entities 120 and anentity associated with a particular entity profile. In certainembodiments, a user computing entity 120 may be configured to query theoccupancy database (or portions of the occupancy database downloaded toand stored locally on the user computing entity 120) for contactinformation/data for a particular entity. The user computing entity 120may thereafter utilize contact information/data stored in an entityprofile for the entity to establish a communication with the entity(e.g., via the entity's user computing entity 120). In variousembodiments, the user computing entity 120 may be configured toautomatically generate and transmit notifications, communications,and/or the like to the entity upon establishing a communication channelwith the entity.

In the item/shipment delivery context, a user computing entity 120associated with delivery personnel may be configured to automaticallyretrieve contact information/data for item/shipment recipients locatedalong the delivery personnel's upcoming delivery route. In certainembodiments, the user computing entity 120 may be configured toautomatically retrieve contact information/data for item/shipmentrecipients upon the occurrence of one or more predefined trigger events,such as a determination that the user computing entity 120 is locatedwithin a predefined distance of the item/shipment delivery locationcorresponding to the entity, upon a determination that the item/shipmentdelivery is expected to occur within a predefined time, upon adetermination that the item/shipment delivery is expected to occurwithin a predefined number of delivery stops, upon a determination thatthe entity is unavailable to accept delivery of the item/shipment 102,and/or the like. Moreover, the communication may be automaticallygenerated (e.g., an automated audio message sent to the entity, anautomated text-based message sent to the entity, and/or the like) ormanually generated (e.g., the delivery personnel manually speaking tothe entity, the delivery personnel manually generating a message to betransmitted to the entity, and/or the like).

Moreover, the user computing entity 120 associated with the deliverypersonnel may be configured to receive and/or process responses receivedfrom the entity. In various embodiments, the entity may be provided withthe option for responding with delivery authorization instructions,“leave-at” instructions indicating a desired location for delivery,and/or the like. The user computing entity 120 may be configured toprovide the entity's response to the delivery personnel at anappropriate time (e.g., upon the occurrence of a trigger event, such asbeing located at a delivery location corresponding to the entity).

As yet another example, the user computing entity 120 associated withthe delivery personnel may be configured to provide a communication tothe entity upon the occurrence of an unsuccessful delivery attempt(e.g., the entity was unavailable to accept delivery and therefore thedelivery personnel did not leave the item/shipment 102 at the intendeddelivery location). The unsuccessful delivery attempt information/datamay comprise information/data identifying an alternative deliverylocation where the item/shipment 102 was delivered, information/dataidentifying a proposed follow-up delivery attempt (e.g., a proposedtime/date for making a second delivery attempt), and/or the like. Again,the user computing entity 120 may be configured to accept and/or utilizea response from the entity, such as indicating instructions for leavingthe item/shipment 102 at an alternative delivery location (e.g., aproperty management office, a delivery locker, an alternative deliverylocation, and/or the like).

6. Enabling Wireless Communication between User Computing Entity andService Point Devices

As noted above in reference to FIG. 4, the entity profile mayadditionally comprise information/data enabling wireless communicationbetween a user computing entity 120 (e.g., a user computing entitycarried by a delivery personnel) and one or more service point devices117 located at a unit/address/service point associated with an entity(e.g., one or more IOT-enabled devices located at an individual'sresidence). The information/data enabling wireless communication betweena user computing entity 120 and one or more service point devices 117may be embodied as security credentials utilized to verify the identityof a trusted user computing entity 120 prior to establishing a wirelesscommunication connection. The security credentials may be stored in theentity profile to enable a user computing entity 120 to present thosesecurity credentials to a service point device 117 without any userinteraction. As discussed herein, the entity profile may comprise anexecutable computer program/file configured to automatically cause theexecuting computing entity (e.g., a user computing entity 120) toestablish a wireless communication interface with one or more servicepoint devices 117 upon the occurrence of one or more trigger events(e.g., moving the executing computing entity within a wirelesscommunication range of the one or more service point devices 117). Theexecutable computer program/file may comprise executable portions forinitiating an appropriate wireless communication interface on anexecuting computing entity (e.g., selecting an appropriate wirelesscommunication interface from Bluetooth, Wi-Fi, NFC, and/or the like viaa user computing entity 120 executing the stored program), for placingthe executing computing entity into a “discoverable” mode that may bedetected by one or more service point devices 117, for initiating avirtual handshake with one or more service point devices 117, forproviding one or more passcodes, security tokens, identity verificationtokens, and/or the like to the service point devices 117, and/or thelike.

As yet another example, the entity profile may comprise information/dataindicative of instructions for establishing a wireless communicationconnection with the one or more service point devices 117 via softwareand/or firmware stored locally on an executing computing entity (e.g.,user computing entity 120). The instructions may compriseinformation/data that may be useable by an executing computing entity(e.g., user computing entity 120) to establish a wireless communicationconnection with a service point device 117, for example, by identifyinga wireless communication interface type utilized to communicate with theservice point device 117, identifying a wireless communication range ofthe service point device 117 (to identify when the executing computingentity can initiate communication with the service point device 117),identifying a password or other security credentials necessary toestablish a wireless communication connection with the service pointdevice 117, and/or the like.

In certain embodiments, the security credentials may be stored withinthe entity profile as multi-use security credentials or one-time-usesecurity credentials. The security credentials may be updated and/orprovided by the entity associated with the entity profile, or thesecurity credentials may be automatically generated by the service pointdevice 117, the occupancy computing entity 100, and/or the like. Inembodiments in which the entity generates and/or updates the securitycredentials, the entity may be enabled to provide the updated securitycredentials directly to the occupancy computing entity 100 for storagein the occupancy database via a user interface provided via adistributed computing entity 110 and/or a user computing entity 120.However, it should be understood that the security credentials may beprovided to a connected computing system, such as a carrier addressmanagement computing entity, which then provides the securitycredentials to the occupancy database. Moreover, the securitycredentials (and/or other information/data necessary for establishing awireless communication connection with the service point device 117) maybe encrypted, hashed, and/or the like to prevent unauthorized users fromgaining access to the information/data.

As just one example, a user computing entity 120 associated with anitem/shipment delivery personnel may establish a wireless communicationconnection with a service point device 117 located at an entity'sunit/address/service point. The user computing entity 120 may gainaccess to the entity profile corresponding to the entity (e.g., bydownloading and locally storing the entity profile prior to approachingthe entity's unit/address/service point to complete an item/shipmentdelivery). The entity profile comprises information/data that may beutilized by the user computing entity 120 to establish a wirelesscommunication connection with the service point device 117 located atthe entity's unit/address/service point (including securitycredentials), and accordingly the user computing entity 120 may beconfigured to initiate a process for establishing the wirelesscommunication connection once the user computing entity 120 is within awireless communication range of the service point device 117. As a partof the process for establishing a wireless communication connection withthe service point device 117, the user computing entity 120 may pass thesecurity credentials to the service point device 117, which may beconfigured to check the provided security credentials against expectedsecurity credentials (e.g., as stored in the occupancy database). Upondetermining that the provided security credentials match the expectedsecurity credentials, the service point device 117 may establish awireless communication connection with the user computing entity 120.

In certain embodiments, once a wireless communication interface isestablished between a user computing entity 120 and a service pointdevice 117, the service point device 117 may be leveraged to determinewhether an individual is available to receive an item/shipment 102 atthe service point. The service point device 117 may thus provideinformation/data to the user computing entity 120 about the status ofthe unit/address/service point associated with the entity. For example,the service point device 117 may be configured to conveyinformation/data to the user computing entity 120, such as whether anindividual is located at the unit/address/service point. In such anexample, item/shipment delivery personnel may utilize theinformation/data to determine whether to attempt to deliver anitem/shipment 102 to the entity. For example, item/shipmentinformation/data corresponding to the item/shipment may indicate thatdelivery of the item/shipment requires a signature from the individualreceiving the item/shipment (e.g., the consignee to whom theitem/shipment is to be delivered and/or an agent thereof). In such anexample, the delivery personnel may skip a delivery attempt to thedelivery location upon a determination that no one is present to acceptdelivery. In such instances, the user computing entity 120 may receiveinformation/data from the service point device 117 indicating that noone is available to accept delivery, and the user computing entity 120may generate a notification for the delivery personnel to skip deliveryto the entity, because a delivery attempt would likely be unsuccessful.

Moreover, in certain embodiments, the user computing entity 120 may beconfigured to generate an electronic delivery confirmation of anitem/shipment 102 based on a wireless communication connection betweenthe user computing entity 120 and the service point device 117. The usercomputing entity 120 may be configured to employ electronic deliveryconfirmation criteria prior to utilizing the electronic deliveryconfirmation. For example, the user computing entity 120 may beconfigured to employ the electronic delivery confirmation upondetermining that an individual is available to accept delivery at theintended destination for an item/shipment 102. Upon determining that theelectronic delivery confirmation criteria has been satisfied, the usercomputing entity 120 may be configured to generate a deliveryconfirmation indication (e.g., to be transmitted to an item/shipmentrecipient's user computing entity 120, to be stored in acarrier-specific computing entity, and/or the like) upon establishing awireless communication connection with the service point device 117.Because the wireless communication protocol associated with servicepoint device 117 has a limited geographical range, the establishment ofa wireless communication connection between the item/shipment deliverypersonnel's user computing entity 120 and the service point device 117indicates that the item/shipment delivery personnel visited theserviceable point corresponding to the item/shipment deliverydestination. In such embodiments, the generated electronic deliveryconfirmation indication may be utilized in lieu of a recipient signatureto evidence delivery of the item/shipment 102 to the destinationlocation.

Moreover, the wireless communication interface established between theuser computing entity 120 and the service point device 117 may enablethe user computing entity 120 to control various mechanisms of theservice point device 117. For example, in embodiments in which theservice point device 117 is a garage door opener (e.g., an IOT enabledgarage door opener) or a door lock (e.g., an IOT enabled door lock), theuser computing entity 120 may be configured to control the garage doorand/or door lock to gain access to the interior of theunit/address/service point (e.g., by opening the garage door orunlocking the door lock). Thus, delivery personnel may be enabled toplace an item/shipment 102 within a secure area of a destinationlocation after the delivery personnel is granted access to the interiorof the destination location. In certain embodiments, the user computingentity 120 and/or the service point device 117 may be configured toautomatically close and/or lock access to the interior of the locationafter delivery has been completed.

7. Identifying Delivery Redirection Options Based on Entity Profile

Upon determining that delivery cannot be completed to an intendeddestination location for an item/shipment 102, item/shipment deliverypersonnel may complete delivery of an item/shipment to an alternativedestination location where the intended item/shipment recipient maypick-up the item/shipment 102 after delivery. In certain embodiments,the entity profile for various entities may identify desired alternativedestination locations for effecting delivery of shipments/items 102after an unsuccessful delivery attempt. The alternative destinationlocations may be identified for particular entity profiles by entitiesassociated with those entity profiles (e.g., via user input generated ata distributed computing entity 110 or user computing entity 120) or thealternative destination locations may be identified automatically, forexample by the occupancy computing entity 100 or distributed computingentity 110 associated with a particular location (e.g., an apartmentcomplex management computing entity). For example, a distributedcomputing entity 110 may automatically identify a property managementoffice as an alternative delivery location for entity profilescorresponding to units/addresses/service points within the property. Asyet another example, the occupancy computing entity 100 may beconfigured to automatically identify nearby item/shipment storagelockers (e.g., identified as being within a threshold distance) as analternative delivery location associated with particular entityprofiles. As yet another example, an entity (e.g., an apartmentresident) may identify one or more neighboring properties as alternativedestination locations for associated entity profiles.

In embodiments in which the occupancy database is in electroniccommunication with a carrier address management database (e.g., managinga carrier loyalty program and storing item/shipment recipient preferenceinformation), the carrier address management database may be configuredto extract information/data from the occupancy database indicative ofpotential alternative delivery destinations for various locations and/orentities. The carrier address management database may be configured toimport those alternative delivery destinations into correspondingprofiles for various entities to provide those entities with options forselecting a preferred alternative delivery destination location. Thecarrier address management database may be configured to transmitinformation/data to the occupancy database indicative of an entity'spreference for an alternative delivery destination, and the occupancydatabase may store an indicator of the entity's preferred alternativedelivery address within an entity profile corresponding to the entity.

In certain embodiments, the occupancy database may store a plurality ofalternative delivery destinations for each of a plurality of entityprofiles, each of the plurality of alternative delivery destinationsbeing applicable for shipments/items 102 satisfying one or morecriteria. For example, a first alternative delivery destination may bepreferred for climate-controlled shipments, and a second alternativedelivery destination may be applicable for non-temperature sensitiveshipments.

V. Conclusion

Many modifications and other embodiments will come to mind to oneskilled in the art to which this disclosure pertains having the benefitof the teachings presented in the foregoing descriptions and theassociated drawings. Therefore, it is to be understood that thedisclosure is not to be limited to the specific embodiments disclosedand that modifications and other embodiments are intended to be includedwithin the scope of the appended claims. Although specific terms areemployed herein, they are used in a generic and descriptive sense onlyand not for purposes of limitation.

That which is claimed:
 1. An automated method for confirming real-timeitem recipient availability via a delivery mobile computing entity incommunication with a central occupancy database, the method comprising:receiving via one or more networks, at the central occupancy databaseand from a plurality of service point devices located at respectiveservice points, each service point device affixed to a building orstructure and associated with a particular customer of a plurality ofcustomers, real-time customer status data for each customer of theplurality of customers, wherein for each customer the real-time customerstatus data indicates whether the customer is located at the associatedservice point; updating availability data stored in customer profiles inthe central occupancy database corresponding to each customer of theplurality of customers to reflect a real-time customer status for eachcustomer; receiving via a wireless communication network, at the centraloccupancy database and from the delivery mobile computing entity, aquery for customer status data for a first customer; retrievingreal-time customer status data for the first customer from a firstcustomer profile corresponding to the first customer; and upondetermining that the real-time customer status data for the firstcustomer indicates that the first customer is available at a servicepoint associated with the first customer, transmitting to the deliverymobile computing entity via the wireless communication network: a)connectivity data, stored in the central occupancy database, for aservice point device associated with the first customer and located atthe service point, the connectivity data enabling the delivery mobilecomputing entity to establish a wireless communication interface betweenthe delivery mobile computing entity and the service point device, andb) an indicator to complete delivery of an item at the service pointassociated with the first customer.
 2. The method of claim 1, furthercomprising, upon determining that the real-time customer status data forthe first customer indicates that the first customer is unavailable,transmit an alternative indicator to the delivery mobile computingentity.
 3. The method of claim 2, wherein the alternative indicatoridentifies an alternative delivery location to complete delivery of theitem.
 4. The method of claim 1, wherein the connectivity data comprisesan executable program which, when executed by the delivery mobilecomputing entity, automatically establishes the wireless communicationinterface between the delivery mobile computing entity and the servicepoint device.
 5. The method of claim 4, wherein the connectivity dataidentifies wireless connectivity data for a customer mobile computingentity associated with the first customer, and wherein transmitting atleast a portion of the connectivity data comprises transmitting thewireless connectivity data to enable wireless communication between thedelivery mobile computing entity associated with a delivery person andthe customer mobile computing entity associated with the first customer.6. The method of claim 1, wherein the query for customer status data forthe first customer comprises a first customer identifier, and retrievingthe real-time customer status data for the first customer comprises:identifying a customer profile having the first customer identifier; andretrieving the real-time customer status data from the identifiedcustomer profile.
 7. A computer system for confirming real-time itemrecipient availability via a delivery mobile computing entity incommunication with a central occupancy database, the system comprising:the delivery mobile computing entity, associated with a delivery person,comprising at least one non-transitory memory storage entity and atleast one processor, wherein the delivery mobile computing entity isconfigured to generate an inquiry to the central occupancy database viaa wireless communication network for customer status data for a firstcustomer scheduled to receive an item delivery; and the centraloccupancy database comprising at least one non-transitory memory storageentity storing a plurality of customer profiles corresponding to aplurality of customers, and wherein the central occupancy database isconfigured to: receive real-time customer status data from a pluralityof service point devices each corresponding to a particular servicepoint and a particular customer, each service point device affixed to abuilding or structure at the particular service point; update thecustomer profiles to reflect the real-time customer status data forcustomers corresponding to each of the customer profiles; receive theinquiry for the customer status data for the first customer via thewireless communication network; retrieve real-time customer status datafor the first customer from a first customer profile corresponding tothe first customer, wherein the real-time customer status data for thefirst customer indicates whether the first customer is located at acorresponding service point, and wherein the first customer profilecomprises connectivity data for a service point device at thecorresponding service point and associated with the first customer; andwhen the real-time customer status data indicates that the firstcustomer is located at the corresponding service point, transmit to thedelivery mobile computing entity via the wireless communication network:a) at least a portion of the connectivity data, the portion of theconnectivity data comprising an executable program which, when executedby the delivery mobile computing entity, automatically establishes awireless communication connection between the delivery mobile computingentity and the service point device, and b) an indicator confirming, inreal time, availability of the first customer for delivery of the itemat the corresponding service point.
 8. The computer system of claim 7,wherein the delivery mobile computing entity is further configured to:receive the real-time customer status data; and generate deliveryconfirmation data after receipt of the real-time customer status data.9. The computer system of claim 8, wherein each of the plurality ofcustomer profiles comprises connectivity data for the correspondingcustomer, and wherein the delivery mobile computing entity is configuredto, based at least in part on the portion of the connectivity data,establish the wireless communication connection between the deliverymobile computing entity and the service point device associated with thefirst customer.
 10. The computer system of claim 9, wherein the deliverymobile computing entity is configured to generate the deliveryconfirmation data upon establishing the wireless communicationconnection with the service point device associated with the firstcustomer.
 11. The computer system of claim 7, wherein the centraloccupancy database is further configured to, upon determining that thecustomer status data for the first customer indicates that the firstcustomer is unavailable, transmit an alternative indicator to thedelivery mobile computing entity.
 12. The computer system of claim 11,wherein the alternative indicator identifies an alternative deliverylocation for completing delivery of the item for the first customer. 13.A computer system for automatically confirming real-time item recipientavailability via a delivery mobile computing entity in communicationwith a central occupancy database, the system comprising one or morenon-transitory memory storage areas and one or more processors, the oneor more processors collectively configured to: receive via a network,from a plurality of service point devices located at respective servicepoints, each service point device affixed to a building or structure andassociated with a particular customer of a plurality of customers,real-time customer status data for each customer of the plurality ofcustomers, wherein for each customer the real-time customer status dataindicates whether the customer is located at the associated servicepoint; update availability data stored in customer profilescorresponding to each customer of the plurality of customers to reflectthe real-time customer status data for each customer; receive via awireless communication network, from the delivery mobile computingentity associated with a delivery person, a query for customer statusdata for a first customer; retrieve, from the one or more non-transitorymemory storage areas, real-time status data for the first customer froma first customer profile corresponding to the first customer; and upondetermining that the real-time customer status data for the firstcustomer indicates that the first customer is available at a servicepoint associated with the first customer, transmit to the deliverymobile computing entity via the wireless communication network: a)connectivity data, retrieved from the central occupancy database, for aservice point device associated with the first customer and located atthe service point, the connectivity data enabling the delivery mobilecomputing entity to establish a wireless communication interface betweenthe delivery mobile computing entity and the service point device, andb) an indicator to complete delivery of an item at the service pointassociated with the first customer.
 14. The computer system of claim 13,wherein the one or more processors are further configured to, upondetermining that the real-time customer status data for the firstcustomer indicates that the first customer is unavailable, transmit analternative indicator to the delivery mobile computing entity.
 15. Thecomputer system of claim 14, wherein the alternative indicatoridentifies an alternative delivery location to complete delivery of theitem.
 16. The computer system of claim 13, wherein the first customerprofile comprises the connectivity data.
 17. The computer system ofclaim 16, wherein the connectivity data identifies wireless connectivitydata for a customer mobile computing entity associated with the firstcustomer, and wherein transmitting at least a portion of theconnectivity data comprises transmitting the wireless connectivity datato enable wireless communication between the delivery mobile computingentity associated with the delivery person and the customer mobilecomputing entity associated with the first customer.
 18. The computersystem of claim 13, wherein the query for first customer status datacomprises a first customer identifier, and retrieving the real-timecustomer status data for the first customer comprises: identifying acustomer profile having the first customer identifier; and retrievingthe real-time customer status data from the identified customer profile.